Control signaling for uplink multiple input multiple output, channel state information reference signal configuration and sounding reference signal configuration

ABSTRACT

Systems, apparatuses, methods, and computer-readable media are provided for time domain resource allocations in wireless communications systems. Disclosed embodiments include time-domain symbol determination and/or indication using a combination of higher layer and downlink control information signaling for physical downlink shared channel and physical uplink shared channel; time domain resource allocations for mini-slot operations; rules for postponing and dropping for multiple mini-slot transmission; and collision handling of sounding reference signals with semi-statically or semi-persistently configured uplink transmissions. Other embodiments may be described and/or claimed.

RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 16/252,294, filed Jan. 18, 2019, which claims priority under 35U.S.C. § 119 to U.S. Provisional App. No. 62/620,176 filed Jan. 22, 2018and U.S. Provisional App. No. 62/651,550 filed Apr. 2, 2018, and claimspriority under 35 U.S.C. § 120 to International App. No.PCT/CN2018/076922 filed Feb. 16, 2018. The contents of each of theaforementioned applications are hereby incorporated by reference intheir entireties.

FIELD

Various embodiments of the present application generally relate to thefield of wireless communications, and in particular, to channel stateinformation reference signal configurations, sounding reference signalconfigurations, and control signaling for uplink multiple input multipleoutput.

BACKGROUND

In the fifth generation (5G) systems, two different transmission schemesare supported for uplink (UL) transmissions. One transmission scheme iscodebook based transmission, and the other transmission schemes isnon-codebook based transmission. For codebook based transmission, a userequipment (UE) can be configured with up to one sounding referencesignal (SRS) resource set with up to two SRS resources. For non-codebookbased transmission, the UE can be configured with up to one SRS resourceset with up to four SRS resources. For each SRS resource, the resourcemapping pattern including frequency offset, comb and number of symbols,antenna port(s), and time domain behavior (e.g., periodic, aperiodic, orsemi-persistent scheduling (SPS) based transmission) can be configuredby radio resource control (RRC) signaling. Therefore, different SRSresources can have different configurations.

Additionally, for uplink codebook based transmission, it is possiblethat the UE is not configured with any SRS resource. In this case, aDemodulation Reference Signal (DM-RS) can be used for link adaptation.The uplink precoder can be selected based on the DMRS. The number ofantenna ports could be the maximum number of layers the UE can support,which can reflect the UE's capability of number of antenna ports.Multi-panel UEs may have multiple DMRS groups and the targetingreceiving next generation NodeB (gNB) may be different.

Furthermore, the channel state information reference signal (CSI-RS) andSRS may be used for CSI estimation and beam management. The CSI-RS mayalso be used for time and frequency offset tracking. There are threetypes of CSI-RS including CSI-RS for CSI acquisition, CSI-RS for layer 1reference signal receiving power (L1-RSRP) computation, and CSI-RS fortracking. Moreover, there are four types of SRS including SRS forcodebook based transmission, SRS for non-codebook transmission, SRS forbeam management, and SRS for antenna switching. However, the three typesof CSI-RS share the same configuration and all the four types of SRSshare the same configuration. This may lead to conflicts or redundantsignaling for some configurations.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 depicts an architecture of a system of a network in accordancewith some embodiments.

FIG. 2 illustrates an example of media access control (MAC) controlelement (CE) based sounding reference signal (SRS) reconfigurationaccording to various embodiments.

FIG. 3a illustrates an example of SRS time domain behavior on a perresource basis according to a first embodiment.

FIG. 3b illustrates an example of SRS time domain behavior on a perresource basis according to a second embodiment.

FIG. 4 illustrates an example SRS triggering mechanism for two types ofSRS resource sets according to various embodiments.

FIG. 5 depicts an architecture of a system including a first corenetwork in accordance with some embodiments.

FIG. 6 depicts an architecture of a system including a second corenetwork in accordance with some embodiments.

FIG. 7 depicts an example of infrastructure equipment in accordance withvarious embodiments.

FIG. 8 depicts example components of a computer platform in accordancewith various embodiments.

FIG. 9 depicts a block diagram illustrating components, according tosome example embodiments, able to read instructions from amachine-readable or computer-readable medium (e.g., a non-transitorymachine-readable storage medium) and perform any one or more of themethodologies discussed herein.

FIG. 10 depicts example components of baseband circuitry and radiofrequency circuitry in accordance with various embodiments.

FIG. 11 is an illustration of various protocol functions that may beused for various protocol stacks in accordance with various embodiments.

FIGS. 12-14 depict example processes for practicing the variousembodiments discussed herein. In particular, FIG. 12 depicts an exampleUL MIMO procedure according to various embodiments; FIG. 13 shows anexample configuration process according to various embodiments; and FIG.14 depicts an example procedure according to various embodiments.

DETAILED DESCRIPTION

Embodiments herein provide mechanisms for control signaling of ULmultiple input multiple output (MIMO). Such embodiments include SRSresource configuration; control signaling for uplink codebook basedtransmission when no SRS resource is configured; and control signalingfor uplink non-codebook based transmission when no SRS resource isconfigured. Additionally, embodiments herein provide mechanisms forsounding reference signal (SRS) and channel state information referencesignal (CSI-RS) configuration. Such embodiments include restriction ofCSI-RS configuration, and restriction of SRS configuration. Otherembodiments may be described and/or claimed.

Referring now to FIG. 1, in which an example architecture of a system100 of a network according to various embodiments, is illustrated. Thefollowing description is provided for an example system 100 thatoperates in conjunction with the LTE system standards and 5G or NRsystem standards as provided by 3GPP technical specifications. However,the example embodiments are not limited in this regard and the describedembodiments may apply to other networks that benefit from the principlesdescribed herein, such as future 3GPP systems (e.g., Sixth Generation(6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), or thelike.

As shown by FIG. 1, the system 100 includes UE 101 a and UE 101 b(collectively referred to as “UEs 101” or “UE 101”). In this example,UEs 101 are illustrated as smartphones (e.g., handheld touchscreenmobile computing devices connectable to one or more cellular networks),but may also comprise any mobile or non-mobile computing device, such asconsumer electronics devices, cellular phones, smartphones, featurephones, tablet computers, wearable computer devices, personal digitalassistants (PDAs), pagers, wireless handsets, desktop computers, laptopcomputers, in-vehicle infotainment (IVI), in-car entertainment (ICE)devices, an Instrument Cluster (IC), head-up display (HUD) devices,onboard diagnostic (OBD) devices, dashtop mobile equipment (DME), mobiledata terminals (MDTs), Electronic Engine Management System (EEMS),electronic/engine control units (ECUs), electronic/engine controlmodules (ECMs), embedded systems, microcontrollers, control modules,engine management systems (EMS), networked or “smart” appliances, MTCdevices, M2M, IoT devices, and/or the like. As discussed in more detailinfra, the UEs 101 incorporate the UL MIMO and CSI-RS and SRSconfiguration embodiments discussed herein. In these embodiments, theUEs 101 are capable of, inter alia, determining SRS resourceconfigurations and/or CSI-RS configurations, and utilize controlsignaling for uplink codebook based transmissions and/or non-codebookbased transmission based on whether SRS resource(s) is/are configured ornot.

In some embodiments, any of the UEs 101 may be IoT UEs, which maycomprise a network access layer designed for low-power IoT applicationsutilizing short-lived UE connections. An IoT UE can utilize technologiessuch as M2M or MTC for exchanging data with an MTC server or device viaa PLMN, ProSe or D2D communication, sensor networks, or IoT networks.The M2M or MTC exchange of data may be a machine-initiated exchange ofdata. An IoT network describes interconnecting IoT UEs, which mayinclude uniquely identifiable embedded computing devices (within theInternet infrastructure), with short-lived connections. The IoT UEs mayexecute background applications (e.g., keep-alive messages, statusupdates, etc.) to facilitate the connections of the IoT network.

The UEs 101 may be configured to connect, for example, communicativelycouple, with an or RAN 110. In embodiments, the RAN 110 may be an NG RANor a 5G RAN, an E-UTRAN, or a legacy RAN, such as a UTRAN or GERAN. Asused herein, the term “NG RAN” or the like refers to a RAN 110 thatoperates in an NR or 5G system 100, and the term “E-UTRAN” or the likerefers to a RAN 110 that operates in an LTE or 4G system 100. The UEs101 utilize connections (or channels) 103 and 104, respectively, each ofwhich comprises a physical communications interface or layer (discussedin further detail below).

In this example, the connections 103 and 104 are illustrated as an airinterface to enable communicative coupling, and can be consistent withcellular communications protocols, such as a GSM protocol, a CDMAnetwork protocol, a PTT protocol, a POC protocol, a UMTS protocol, a3GPP LTE protocol, a 5G protocol, a NR protocol, and/or any of the othercommunications protocols discussed herein. In embodiments, the UEs 101may directly exchange communication data via a ProSe interface 105. TheProSe interface 105 may alternatively be referred to as a SL interface105 and may comprise one or more logical channels, including but notlimited to a PSCCH, a PSSCH, a PSDCH, and a PSBCH.

The UE 101 b is shown to be configured to access an AP 106 (alsoreferred to as “WLAN node 106,” “WLAN 106,” “WLAN Termination 106,” “WT106” or the like) via connection 107. The connection 107 can comprise alocal wireless connection, such as a connection consistent with any IEEE802.11 protocol, wherein the AP 106 would comprise a WiFi® router. Inthis example, the AP 106 is shown to be connected to the Internetwithout connecting to the core network of the wireless system (describedin further detail below). In various embodiments, the UE 101 b, RAN 110,and AP 106 may be configured to utilize LWA operation and/or LWIPoperation. The LWA operation may involve the UE 101 b in RRC_CONNECTEDbeing configured by a RAN node 111 a-b to utilize radio resources of LTEand WLAN. LWIP operation may involve the UE 101 b using WLAN radioresources (e.g., connection 107) via IPsec protocol tunneling toauthenticate and encrypt packets (e.g., IP packets) sent over theconnection 107. IPsec tunneling may include encapsulating the entiretyof original IP packets and adding a new packet header, therebyprotecting the original header of the IP packets.

The RAN 110 can include one or more AN nodes or RAN nodes 111 a and 111b (collectively referred to as “RAN nodes 111” or “RAN node 111”) thatenable the connections 103 and 104. As used herein, the terms “accessnode,” “access point,” or the like may describe equipment that providesthe radio baseband functions for data and/or voice connectivity betweena network and one or more users. These access nodes can be referred toas BS, gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs or TRPs, and so forth,and can comprise ground stations (e.g., terrestrial access points) orsatellite stations providing coverage within a geographic area (e.g., acell). As used herein, the term “NG RAN node” or the like refers to aRAN node 111 that operates in an NR or 5G system 100 (for example, agNB), and the term “E-UTRAN node” or the like refers to a RAN node 111that operates in an LTE or 4G system 100 (e.g., an eNB). According tovarious embodiments, the RAN nodes 111 may be implemented as one or moreof a dedicated physical device such as a macrocell base station, and/ora low power (LP) base station for providing femtocells, picocells orother like cells having smaller coverage areas, smaller user capacity,or higher bandwidth compared to macrocells.

In some embodiments, all or parts of the RAN nodes 111 may beimplemented as one or more software entities running on server computersas part of a virtual network, which may be referred to as a CRAN and/ora virtual baseband unit pool (vBBUP). In these embodiments, the CRAN orvBBUP may implement a RAN function split, such as a PDCP split whereinRRC and PDCP layers are operated by the CRAN/vBBUP and other L2 protocolentities are operated by individual RAN nodes 111; a MAC/PHY splitwherein RRC, PDCP, RLC, and MAC layers are operated by the CRAN/vBBUPand the PHY layer is operated by individual RAN nodes 111; or a “lowerPHY” split wherein RRC, PDCP, RLC, MAC layers and upper portions of thePHY layer are operated by the CRAN/vBBUP and lower portions of the PHYlayer are operated by individual RAN nodes 111. This virtualizedframework allows the freed-up processor cores of the RAN nodes 111 toperform other virtualized applications. In some implementations, anindividual RAN node 111 may represent individual gNB-DUs that areconnected to a gNB-CU via individual F1 interfaces (not shown by FIG.1). In these implementations, the gNB-DUs may include one or more remoteradio heads or RFEMs (see, e.g., FIG. 7), and the gNB-CU may be operatedby a server that is located in the RAN 110 (not shown) or by a serverpool in a similar manner as the CRAN/vBBUP. Additionally oralternatively, one or more of the RAN nodes 111 may be next generationeNBs (ng-eNBs), which are RAN nodes that provide E-UTRA user plane andcontrol plane protocol terminations toward the UEs 101, and areconnected to a 5GC (e.g., CN 620 of FIG. 6) via an NG interface(discussed infra).

In V2X scenarios one or more of the RAN nodes 111 may be or act as RSUs.The term “Road Side Unit” or “RSU” refers to any transportationinfrastructure entity used for V2X communications. An RSU may beimplemented in or by a suitable RAN node or a stationary (or relativelystationary) UE, where an RSU implemented in or by a UE may be referredto as a “UE-type RSU,” an RSU implemented in or by an eNB may bereferred to as an “eNB-type RSU,” an RSU implemented in or by a gNB maybe referred to as a “gNB-type RSU,” and the like. In one example, an RSUis a computing device coupled with radio frequency circuitry located ona roadside that provides connectivity support to passing vehicle UEs 101(vUEs 101). The RSU may also include internal data storage circuitry tostore intersection map geometry, traffic statistics, media, as well asapplications/software to sense and control ongoing vehicular andpedestrian traffic. The RSU may operate on the 5.9 GHz Direct ShortRange Communications (DSRC) band to provide very low latencycommunications required for high speed events, such as crash avoidance,traffic warnings, and the like. Additionally or alternatively, the RSUmay operate on the cellular V2X band to provide the aforementioned lowlatency communications, as well as other cellular communicationsservices. Additionally or alternatively, the RSU may operate as a Wi-Fihotspot (2.4 GHz band) and/or provide connectivity to one or morecellular networks to provide uplink and downlink communications. Thecomputing device(s) and some or all of the radiofrequency circuitry ofthe RSU may be packaged in a weatherproof enclosure suitable for outdoorinstallation, and may include a network interface controller to providea wired connection (e.g., Ethernet) to a traffic signal controllerand/or a backhaul network.

Any of the RAN nodes 111 can terminate the air interface protocol andcan be the first point of contact for the UEs 101. In some embodiments,any of the RAN nodes 111 can fulfill various logical functions for theRAN 110 including, but not limited to, radio network controller (RNC)functions such as radio bearer management, uplink and downlink dynamicradio resource management and data packet scheduling, and mobilitymanagement.

In embodiments, the UEs 101 can be configured to communicate using OFDMcommunication signals with each other or with any of the RAN nodes 111over a multicarrier communication channel in accordance with variouscommunication techniques, such as, but not limited to, an OFDMAcommunication technique (e.g., for downlink communications) or a SC-FDMAcommunication technique (e.g., for uplink and ProSe or sidelinkcommunications), although the scope of the embodiments is not limited inthis respect. The OFDM signals can comprise a plurality of orthogonalsubcarriers.

Downlink and uplink transmissions may be organized into frames with 10ms durations, where each frame includes ten 1 ms subframes. A slotduration is 14 symbols with Normal CP and 12 symbols with Extended CP,and scales in time as a function of the used sub-carrier spacing so thatthere is always an integer number of slots in a subframe. In someembodiments, a downlink resource grid can be used for downlinktransmissions from any of the RAN nodes 111 to the UEs 101, while uplinktransmissions can utilize similar techniques. The grid can be atime-frequency grid, called a resource grid or time-frequency resourcegrid, which is the physical resource in the downlink in each slot. Sucha time-frequency plane representation is a common practice for OFDMsystems, which makes it intuitive for radio resource allocation. Eachcolumn and each row of the resource grid corresponds to one OFDM symboland one OFDM subcarrier, respectively. The duration of the resource gridin the time domain corresponds to one slot in a radio frame. Thesmallest time-frequency unit in a resource grid is denoted as a resourceelement. Each resource grid comprises a number of resource blocks, whichdescribe the mapping of certain physical channels to resource elements.Each resource block comprises a collection of resource elements; in thefrequency domain, this may represent the smallest quantity of resourcesthat currently can be allocated. There are several different physicaldownlink channels that are conveyed using such resource blocks.

The PDSCH carries user data and higher-layer signaling to the UEs 101.Typically, downlink scheduling (assigning control and shared channelresource blocks to the UE 101 b within a cell) may be performed at anyof the RAN nodes 111 based on channel quality information fed back fromany of the UEs 101. The downlink resource assignment information may besent on the PDCCH used for (e.g., assigned to) each of the UEs 101. ThePDCCH can be used to schedule DL transmissions on PDSCH and ULtransmissions on PUSCH, where the DCI on PDCCH includes, inter alia,downlink assignments containing at least modulation and coding format,resource allocation, and HARQ information related to DL-SCH; and/oruplink scheduling grants containing at least modulation and codingformat, resource allocation, and HARQ information related to UL-SCH. Inaddition to scheduling, the PDCCH can be used to for activation anddeactivation of configured PUSCH transmission with configured grant;activation and deactivation of PDSCH semi-persistent transmission;notifying one or more UEs 101 of a slot format; notifying one or moreUEs 101 of the PRB(s) and OFDM symbol(s) where a UE 101 may assume notransmission is intended for the UE; transmission of TPC commands forPUCCH and PUSCH; transmission of one or more TPC commands for SRStransmissions by one or more UEs; switching an active BWP for a UE 101;and initiating a random access procedure.

The PDCCH uses CCEs to convey the control information. Control channelsare formed by aggregation of one or more CCEs, where different coderates for the control channels are realized by aggregating differentnumbers of CCEs. Before being mapped to resource elements, the PDCCHcomplex-valued symbols may first be organized into quadruplets, whichmay then be permuted using a sub-block interleaver for rate matching.Each PDCCH is transmitted using one or more of these CCEs, where eachCCE may correspond to nine sets of four physical resource elements knownas REGs. Four QPSK symbols may be mapped to each REG. The PDCCH can betransmitted using one or more CCEs, depending on the size of the DCI andthe channel condition. For example, there can be four or more differentPDCCH formats defined in LTE with different numbers of CCEs (e.g.,aggregation level, L=1, 2, 4, or 8).

The UEs 101 monitor (or attempt to decode) respective sets of PDCCHcandidates in one or more configured monitoring occasions according tothe corresponding search space configurations. In NR implementations,the UEs 101 monitor (or attempt to decode) respective sets of PDCCHcandidates in one or more configured monitoring occasions in one or moreconfigured CORESETs according to the corresponding search spaceconfigurations. A CORESET includes a set of PRBs with a time duration of1 to 3 OFDM symbols. The REGs and CCEs are defined within a CORESET witheach CCE including a set of REGs. Interleaved and non-interleavedCCE-to-REG mapping are supported in a CORESET. Each REG carrying PDCCHcarries its own DMRS.

Some embodiments may use concepts for resource allocation for controlchannel information that are an extension of the above-describedconcepts. For example, some embodiments may utilize an EPDCCH that usesPDSCH resources for control information transmission. The EPDCCH may betransmitted using one or more ECCEs. Similar to above, each ECCE maycorrespond to nine sets of four physical resource elements known as anEREGs. An ECCE may have other numbers of EREGs in some situations.

PUSCH transmission(s) can be dynamically scheduled by an UL grant in aDCI, or the transmission can correspond to a configured grant typeincluding Type 1 or Type 2. The configured grant Type 1 PUSCHtransmission is semi-statically configured to operate upon the receptionof higher layer parameter of configuredGrantConfig includingrrc-ConfiguredUplinkGrant without the detection of an UL grant in a DCI.The configured grant Type 2 PUSCH transmission is semi-persistentlyscheduled by an UL grant in a valid activation DCI after the receptionof higher layer parameter configurdGrantConfig not includingrrc-ConfiguredUplinkGrant.

For the PUSCH transmission corresponding to a configured grant, theparameters applied for the transmission are provided byconfiguredGrantConfig expect for dataScramblingIdentityPUSCH, txConfig,codebookSubset, maxRank, scaling of UCI-OnPUSCH, which are provided bypusch-Config. If the UE 101 is provided with transformPrecoder inconfiguredGrantConfig, the UE 101 applies the higher layer parametertp-pi2BPSK, if provided in pusch-Config for the PUSCH transmissioncorresponding to a configured grant.

For the PUSCH retransmission scheduled by a PDCCH with CRC scrambled byCS-RNTI with NDI=1, the parameters in pusch-Config are applied for thePUSCH transmission except for p0-NominalWithoutGrant, p0-PUSCH-Alpha,powerControlLoopToUse, pathlossReferenceIndex, mcs-Table,mcs-TableTransformPrecoder, and transformPrecoder.

The UE 101, upon detection of a PDCCH with a configured DCI (e.g., DCIformat 0_0 or 0_1), transmits the corresponding PUSCH as indicated bythat DCI. Upon detection of a DCI format 0_1 with an “UL-SCH indicator”set to “0” and with a non-zero (or NZP) “CSI request” where theassociated “reportQuantity” in CSI-ReportConfig set to “none” for allCSI report(s) triggered by “CSI request” in this DCI format 0_1, the UE101 ignores all fields in this DCI except the “CSI request” and the UE101 does not transmit the corresponding PUSCH as indicated by this DCIformat 0_1. For any two HARQ process IDs in a given scheduled cell, ifthe UE 101 is scheduled to start a first PUSCH transmission starting insymbol j by a PDCCH ending in symbol i, the UE is not expected to bescheduled to transmit a PUSCH starting earlier than the ending symbol ofthe first PUSCH by a PDCCH that does not end earlier than symbol i. TheUE is not expected to be scheduled to transmit another PUSCH by DCIformat 0_0 or 0_1 scrambled by C-RNTI or MCS-C-RNTI for a given HARQprocess until after the end of the expected transmission of the lastPUSCH for that HARQ process. For PUSCH scheduled by DCI format 0_0 on acell, the UE 101 transmits PUSCH according to the spatial relation, ifapplicable, corresponding to the PUCCH resource with the lowestidentifier (ID) within the active UL BWP of the cell.

Two transmission schemes are supported for PUSCH including a codebookbased transmission scheme and non-codebook based transmission scheme.The UE 101 is configured with the codebook based transmission schemewhen the higher layer (e.g., RRC) parameter txConfig in pusch-Config isset to ‘codebook’, and the UE 101 is configured for the non-codebookbased transmission scheme when the higher layer parameter txConfig isset to ‘nonCodebook’. If the higher layer parameter txConfig is notconfigured, the UE 101 is not expected to be scheduled by DCI format0_1. If PUSCH is scheduled by DCI format 0_0, the PUSCH transmission isbased on a single antenna port, and the UE 101 does not expect PUSCHscheduled by DCI format 0_0 in a BWP without configured PUCCH resourcewith PUCCH-SpatialRelationInfo in frequency range 2 in RRC connectedmode.

For codebook based transmission, the PUSCH can be scheduled by DCIformat 0_0, DCI format 0_1, or semi-statically configured to operate. Ifthe PUSCH is scheduled by DCI format 0_1, or semi-statically configuredto operate, the UE 101 determines its PUSCH transmission precoder basedon SRI, TPMI and the transmission rank, where the SRI, TPMI and thetransmission rank are provided the SRS resource indicator field and theprecoding information and number of layers field of the DCI, or given bythe higher layer parameters srs-ResourceIndicator andprecodingAndNumberOfLayers. The TPMI is used to indicate the precoder tobe applied over the antenna ports and/or layers {0 . . . ν−1} and thatcorresponds to the SRS resource selected by the SRI when multiple SRSresources are configured, or if a single SRS resource is configured TPMIis used to indicate the precoder to be applied over the antenna portsand/or layers {0 . . . ν−1} and that corresponds to the SRS resource.The transmission precoder is selected from the uplink codebook that hasa number of antenna ports equal to higher layer parameter nrofSRS-Portsin SRS-Config. According to various embodiments, when the UE 101 isconfigured with the higher layer parameter txConfig set to ‘codebook’,the UE 101 is configured with at least one SRS resource. The indicatedSRI in slot n is associated with the most recent transmission of SRSresource identified by the SRI, where the SRS resource is prior to thePDCCH carrying the SRI. In some embodiments, the SRS resource is priorto the PDCCH carrying the SRI before slot n.

An individual SRS resource can be used for different purposes: codebookbased transmission, non-codebook based transmission, beam management,and/or antenna switching. Different SRS resources can have differentconfiguration of resource mapping pattern including frequency offset,comb and number of symbols, antenna port(s), and time domain behavior(periodic, aperiodic or semi-persistent (SPS) based transmission) by RRCsignaling. However, since the number of SRS resources are limited for ULcodebook based and UL non-codebook based transmission, to change somecontrol signaling of SRS may rely on RRC signaling, which has a largelatency. Further there can be only 1 SRS resource set for eachtransmissions scheme, then one possible way is that all the SRSresources can have the same time domain behavior, but this may result inonly 1 time domain behavior is supported. If the SRS resources can havedifferent time domain behavior, how to trigger the SRS resources couldbe one issue and some scheduling restriction may be necessary.

FIG. 2 illustrates an example of MAC control element (CE) based SRSreconfiguration according to various embodiments. In these embodiments,for SRS resources used for codebook or non-codebook based transmissionor beam management, at least some of its configuration can be updated byMAC CE to reduce the reconfiguration latency. The MAC CE can include theSRS resource ID and at least one of the new configurations of theresource mapping pattern including frequency offset, comb and number ofsymbols, cyclic shifts, sequence ID, antenna port(s), and time domainbehavior (periodic, aperiodic or semi-persistent (SPS) basedtransmission). For example, as shown by FIG. 2, the SRS Resource 1 isinitially configured to be periodic and have a comb of 2 at point 205,and at point 210, the MAC CE updates the comb of SRS Resource 1 to be 4.Then at point 215, the periodic SRS is transmitted over SRS resource 1with comb equal to 4. For one SRS resource, if the antenna port(s) arechanged, different UE transmitting beams can be applied.

FIG. 3a illustrates an example of SRS time domain behavior on a perresource basis according to a first embodiment, and FIG. 3b illustratesan example of SRS time domain behavior on a per resource basis accordingto a second embodiment. In these embodiments, the aperiodic SRS can betriggered by the SRS request indicator/field in the DCI, and only theSRS resource with the configuration of aperiodic transmission in thetriggered SRS resource set can be triggered. For example, as shown byFIG. 3a , SRS Resource 1 is configured to be periodic, which istransmitted at point 305. At point 310, a PDCCH is obtained, whichincludes a DCI that triggers transmission of an aperiodic SRS in SRSresource 2 at point 315. Alternatively, the SRS resources in thetriggered SRS resource set can be triggered regardless of its timedomain behavior configuration. For example, as shown by FIG. 3b , atpoint 320 a periodic SRS and/or an aperiodic SRS are transmitted overSRS resource 1 and SRS resource 2, respectively. At point 325, a PDCCHis obtained, which includes a DCI that triggers one or both of theperiodic or aperiodic SRS transmissions at point 330. Further, forperiodic and SPS SRS, its transmission can be based on the configurationof time domain behavior per SRS resource. Alternatively, it can be perSRS resource set basis. Then if one SRS resource in the resource set isconfigured with corresponding time domain behavior, e.g. periodictransmission, the whole SRS resource set can be transmittedperiodically.

In some embodiments, it may be possible that one SRS resource is nottransmitted while triggered by the RAN node 111 (e.g., a gNB). Forcodebook based transmission, the number of antenna ports should be basedon the maximum number of layers or the number of antenna ports for theindicated SRS resource. Alternatively, for codebook based ornon-codebook based transmission, the SRS resource which has not beentransmitted should not be indicated by the SRS resource indicator (SRI)in uplink grant. In other words, if there is only 1 SRS resourceconfigured by RRC, there may be no SRI indicated in the DCI.

In other embodiments, the SRS resources used for different resource setcan be triggered by one DCI. Then there can be two different types ofSRS resource set: type 1 SRS resource set is based on the function ofthe SRS resource and type 2 SRS resource is based on the aperiodictransmission behavior. The SRS resource configured with the periodic orSPS transmission should not be configured with a type 2 SRS resource setindex. Then in the DCI, the aperiodic SRS transmission is based on thetype 2 SRS resource set index.

In other embodiments, for non-codebook based transmission, the bandwidthof SRS transmission and its configured CSI-RS should be configured to bewithin a margin, since the UE should derive the uplink precoder based onthe CSI-RS, and apply it to the SRS. In an example, the bandwidth of SRSshould be within the bandwidth of CSI-RS. In another example, thebandwidth of SRS can be configured with X RB offset compared to that ofCSI-RS, where X is up to X_max, where X_max can be pre-defined ordetermined by the system bandwidth.

FIG. 4 illustrates an example SRS triggering mechanism for two types ofSRS resource sets according to various embodiments. In theseembodiments, for codebook based transmission scheme and/or non-codebookbased transmission scheme, at least one SRS resource for a currenttransmission scheme should be configured. If no SRS resource isconfigured, the UE 101 should use a fallback mode, which is triggered byfallback DCI, which in some embodiments may be a DCI format 0_0. Forexample, as shown by FIG. 4, at point 410, a PDCCH is obtained thatincludes a DCI with no SRS request field, which triggers a fallbackaperiodic SRS transmission at point 415. In the fallback mode, theuplink beam indication can be based on the RRC or RRC and MAC CE, or theuplink beam for PUSCH should be the same as one PUCCH resource, whichcan be predefined, for example, the PUCCH resource with lowest resourceID, or configured by RRC signaling.

In other embodiments, if the UE 101 is configured with codebook basedtransmission scheme and no SRS for this transmissions scheme isconfigured, the number of antenna ports to determine the precoder can bedetermined by the number of or index(es) of scheduled DMRS group indexand its maximum number of layers or maximum number of layers per DMRSgroups. In one example, the number of antenna ports can be Σ_(j∈S)N_(j)where S is the set of scheduled DMRS group index and N_(j) is themaximum number of layers for current DMRS group.

In one example, the UE 101 may have 2 panels with 2 antenna ports perpanel, and if the transmission is based on one panel, one DMRS group maybe indicated and then the precoder should be based on 2 antenna portscodebook; if both panels are scheduled, the precoder should be based on4 antenna ports codebook.

In other embodiments, if the UE 101 is configured with non-codebookbased transmission scheme and no SRS for this transmissions scheme isconfigured, the rank of the precoder can be determined by the number ofscheduled DMRS antenna ports and the precoder can be selected by the UE101, which can be based on UE implementation or associated with oneprevious DMRS precoder, which can be configured by the RAN node 111(e.g., gNB) or defined based on a rule, for example, the latest DMRStransmission before slot n-k, where n is current slot and k can beconfigured by higher layer signaling or fixed, for example at 4.

In other embodiments, if no SRS is configured for the UE, the 1-porttransmission can be used. The RAN node 111 (e.g., gNB) can indicate theTPMI based on the rank1 and non-coherent transmission precoders toselect the antenna port of PUSCH. Alternatively, the UE 101 couldfallback to transmit diversity mode, where the RAN node 111 (e.g., gNB)can define the number of Precoder Resource block Group (PRG) or the PRGsize, and/or codebook sub-set restriction, and the UE 101 can randomlyselect the precoder for each PRG. Further, if there is no beamcorrespondence and no SRS is configured, the UE 101 can follow the sametransmission scheme as initial access messages, e.g. message 1 ormessage 3.

In embodiments, in a SRS resource set, the following signaling may beconfigured: SRS-AssocCSI-RS and SRS-SetUse. The SRS-AssocCSI-RS is usedto identify the CSI-RS resource used for downlink channel estimation fornon-codebook based uplink transmission. Then the uplink precoder can bederived based on the estimated channel. Thus, this parameter impliesthat the SRS resources in a resource set for non-codebook basedtransmission should share the same Tx beam. The SRS-SetUse is used toidentify the type of the SRS resource set: codebook based transmission,non-codebook based transmission, beam management or antenna switching.

In embodiments, in each SRS resource, the following signaling may beconfigured SRS-SpatialRelationInfo. The SRS-SpatialRelationInfo may beused to indicate the Tx beam of the SRS resource, which can be, forexample, a Synchronization Signal Block (SSB) or CSI-RS Resource Index(CRI) or SRS Resource Index (SRI). Then there may be some conflictregarding the parameters above. In some embodiments, whenSRS-AssocCSI-RS is configured, the UE 101 is be expected to beconfigured with the same value of SRS-SpatialRelationInfo and thereference signal indicated by SRS-SpatialRelationInfo should bespatially associated with the CSI-RS indicated by SRS-AssocCSI-RS. Inother embodiments, the SRS power control parameters may be configuredper resource set, so that the SRS-SpatialRelationInfo should beconfigured to be the same for SRS resource in a resource set for sometypes of SRS, for example, codebook based transmission, non-codebookbased transmission, beam management or antenna switching. In such otherembodiments, the downlink reference signal for power control should bespatially associated with the reference signal indicated bySRS-SpatialRelationInfo.

Further, for a SRS resource set for beam management, theSRS-SpatialRelationInfo may be configured to be the reference Tx beam;the UE 101 may then select the Tx beam for the SRS resources around thisTx beam. In some embodiments, for a SRS resource set used fornon-codebook based transmission, which is configured to besemi-persistent, the spatial relation configured in the MAC CE toactivate all/some of the SRS resources in the set should be configuredto be the same. In other embodiments, for uplink codebook basedtransmission, if the SRS resource(s) are configured to besemi-persistent, the UE 101 expects such SRS resource(s) should beactivated and use the same spatial domain filter to transmit the PUSCHas the activated SRS resource for codebook based transmission.Alternatively, if such SRS resource(s) are not activated, the UE 101applies the same spatial domain filter to transmit the PUSCH as theparameter SRS-SpatialRelationInfo configured for the indicated SRS. Inanother option, the PUSCH beam should be the same as the beam used for aparticular PUCCH resource or a particular SRS resource for beammanagement.

Referring back to FIG. 1, for codebook based transmissions, the UE 101determines its codebook subsets based on TPMI and upon the reception ofhigher layer parameter codebookSubset in pusch-Config which may beconfigured with ‘fullyAndPartialAndNonCoherent’,‘partialAndNonCoherent’, or ‘nonCoherent’ depending on the UEcapability. The maximum transmission rank may be configured by thehigher parameter maxRank in pusch-Config. When the UE 101 reports a UEcapability of ‘partialAndNonCoherent’ transmission, the UE 101 does notexpect to be configured by codebookSubset with‘fullyAndPartialAndNonCoherent’. When the UE 101 reports a UE capabilityof ‘nonCoherent’ transmission, the UE 101 does not expect to beconfigured by codebookSubset with ‘fullyAndPartialAndNonCoherent’ orwith ‘partialAndNonCoherent’. The UE 101 does not expect to beconfigured with the higher layer parameter codebookSubset set to‘partialAndNonCoherent’ when higher layer parameter nrofSRS-Ports in anSRS-ResourceSet with usage set to ‘codebook’ indicates that two SRSantenna ports are configured.

For codebook based transmissions, the UE 101 may be configured with asingle SRS-ResourceSet with usage set to ‘codebook’ and only one SRSresource can be indicated based on the SRI from within the SRS resourceset. The maximum number of configured SRS resources for codebook basedtransmission is 2. If aperiodic SRS is configured for the UE 101, theSRS request field in the DCI triggers the transmission of aperiodic SRSresources. The UE 101 transmits PUSCH using the same antenna port(s) asthe SRS port(s) in the SRS resource indicated by the DCI format 0_1 orby configuredGrantConfig. When multiple SRS resources are configured bySRS-ResourceSet with usage set to ‘codebook’, the UE 101 is to expectthat higher layer parameters nrofSRS-Ports in SRS-Resource inSRS-ResourceSet shall be configured with the same value for all theseSRS resources.

The SRS request field in DCI format 0_1 and 1_1 is 2 bits as defined bytable 1 for UEs 101 not configured with SUL in the cell; 3 bits for UEs101 configured SUL in the cell where the first bit is the non-SUL/SULindicator and the second and third bits are defined by table 1. This bitfield may also indicate the associated CSI-RS as discussed elsewhereherein. Additionally, DCI format 2_3 may also have a 2 bit SRS requestfield as defined by table 1.

TABLE 1 SRS request Triggered aperiodic SRS resource set(s) for DCIformat 0_1, 1_0, and 2_3 configured with higher layer Triggeredaperiodic SRS resource set(s) for DCI Value of SRS parametersrs-TPC-PDCCH-Group format 2_3 configured with higher layer requestfield set to ‘typeB’ parameter srs-TPC-PDCCH-Group set to ‘typeA’ 00 Noaperiodic SRS resource set No aperiodic SRS resource set triggeredtriggered 01 SRS resource set(s) configured with SRS resource set(s)configured with higher layer higher layer parameter aperiodicSRS-parameter SRS-SetUse set to ‘antenna switching’ ResourceTrigger set to 1and resourceType in SRS-ResourceSet set to ‘aperiodic’ for a 1^(st) setof serving cells configured by higher layers 10 SRS resource set(s)configured with SRS resource set(s) configured with higher layer higherlayer parameter aperiodicSRS- parameter SRS-SetUse set to ‘antennaswitching’ ResourceTrigger set to 2 and resourceType in SRS-ResourceSetset to ‘aperiodic’ for a 2^(nd) set of serving cells configured byhigher layers 11 SRS resource set(s) configured with SRS resource set(s)configured with higher layer higher layer parameter aperiodicSRS-parameter SRS-SetUse set to ‘antenna switching’ ResourceTrigger set to 3and resourceType in SRS-ResourceSet set to ‘aperiodic’ for a 3^(rd) setof serving cells configured by higher layers

For non-codebook based transmission, PUSCH can be scheduled by DCIformat 0_0, DCI format 0_1, or semi-statically configured to operate.The UE 101 can determine its PUSCH precoder and transmission rank basedon the SRI when multiple SRS resources are configured, where the SRI isgiven by the SRS resource indicator in DCI, or the SRI is given bysrs-ResourceIndicator. The UE 101 uses one or multiple SRS resources forSRS transmission, where, in a SRS resource set, the maximum number ofSRS resources which can be configured to the UE for simultaneoustransmission in the same symbol and the maximum number of SRS resourcesare UE capabilities. Only one SRS port for each SRS resource isconfigured. Only one SRS resource set can be configured with higherlayer parameter usage in SRS-ResourceSet set to ‘nonCodebook’. Themaximum number of SRS resources that can be configured for non-codebookbased uplink transmission is 4. The indicated SRI in slot n isassociated with the most recent transmission of SRS resource(s)identified by the SRI, where the SRS transmission is prior to the PDCCHcarrying the SRI. In some embodiments, the SRS transmission is prior tothe PDCCH carrying the SRI before slot n.

For non-codebook based transmission, the UE 101 can calculate theprecoder used for the transmission of SRS based on measurement of anassociated NZP CSI-RS resource. The UE 101 can be configured with onlyone NZP CSI-RS resource for the SRS resource set with higher layerparameter usage in SRS-ResourceSet set to ‘nonCodebook’ if configured.

If aperiodic SRS resource set is configured, the associated NZP-CSI-RSis indicated via SRS request field in DCI format 0_1 and 1_1, whereAperiodicSRS-ResourceTrigger indicates the association between aperiodicSRS triggering state and SRS resource sets, triggered SRS resource(s)srs-ResourceSetId, csi-RS indicating the associatedNZP-CSI-RS-ResourceId are higher layer configured in SRS-ResourceSet.The UE 101 is not expected to update the SRS precoding information ifthe gap from the last symbol of the reception of the aperiodicNZP-CSI-RS resource and the first symbol of the aperiodic SRStransmission is less than 42 OFDM symbols.

If the UE 101 is configured with aperiodic SRS associated with aperiodicNZP CSI-RS resource, the presence of the associated CSI-RS is indicatedby the SRS request field if the value of the SRS request field is not‘00’ and if the scheduling DCI is not used for cross carrier or crossbandwidth part scheduling. The CSI-RS is located in the same slot as theSRS request field. If the UE configured with aperiodic SRS associatedwith aperiodic NZP CSI-RS resource, any of the TCI states configured inthe scheduled CC shall not be configured with ‘QCL-TypeD’.

If periodic or semi-persistent SRS resource set is configured, theNZP-CSI-RS-ResourceConfigID for measurement is indicated via higherlayer parameter associatedCSI-RS in SRS-ResourceSet. The UE 101 performsone-to-one mapping from the indicated SRI(s) to the indicated DM-RSports(s) and their corresponding PUSCH layers {0 . . . ν−1} given by DCIformat 0_1 or by configuredGrantConfig in increasing order. The UE 101transmits PUSCH using the same antenna ports as the SRS port(s) in theSRS resource(s) indicated by SRI(s) given by DCI format 0_1 or byconfiguredGrantConfig, where the SRS port in (i+1)-th SRS resource inthe SRS resource set is indexed as p_(i)=1000+i.

For non-codebook based transmission, the UE 101 does not expect to beconfigured with both spatialRelationInfo for SRS resource andassociatedCSI-RS in SRS-ResourceSet for SRS resource set. Fornon-codebook based transmission, the UE 101 can be scheduled with DCIformat 0_1 when at least one SRS resource is configured inSRS-ResourceSet with usage set to ‘nonCodebook’.

The UE 101 can be configured with one or more Sounding Reference Signal(SRS) resource sets as configured by the higher layer parameterSRS-ResourceSet. For each SRS resource set, a UE may be configured withK≥1 SRS resources (e.g., by higher layer parameter SRS-Resource), wherethe maximum value of K is indicated by, for example, SRS_capability. TheSRS resource set applicability is configured by the higher layerparameter usage in SRS-ResourceSet. When the higher layer parameterusage is set to ‘BeamManagement’, only one SRS resource in each ofmultiple SRS sets can be transmitted at a given time instant, the SRSresources in different SRS resource sets with the same time domainbehavior in the same BWP can be transmitted simultaneously.

For aperiodic SRS at least one state of the DCI field is used to selectat least one out of the configured SRS resource set(s). The followingSRS parameters are semi-statically configurable by higher layerparameter SRS-Resource:

-   -   srs-ResourceId determines SRS resource configuration identify.    -   Number of SRS ports as defined by the higher layer parameter        nrofSRS-Ports.    -   Time domain behaviour of SRS resource configuration as indicated        by the higher layer parameter resource Type, which can be        periodic, semi-persistent, aperiodic SRS transmission.    -   Slot level periodicity and slot level offset as defined by the        higher layer parameters periodicityAndOffset-p or        periodiciAndOffset-sp for an SRS resource of type periodic or        semi-persistent. The UE shall not expect to be configured with        SRS resources in the same SRS resource set SRS-ResourceSet with        different slot level periodicities. For an SRS-ResourceSet        configured with higher layer parameter resource Type set to        ‘aperiodic’, a slot level offset is defined by the higher layer        parameter slotOffset.    -   Number of OFDM symbols in the SRS resource, starting OFDM symbol        of the SRS resource within a slot including repetition factor R        as defined by the higher layer parameter resourceMapping.    -   SRS bandwidth B_(SRS) and C_(SRS), as defined by the higher        layer parameter freqHopping.    -   Frequency hopping bandwidth, b_(hop), as defined by the higher        layer parameter freqHopping.    -   Defining frequency domain position and configurable shift as        defined by the higher layer parameters freqDomainPosition and        freqDomainShift, respectively.    -   Cyclic shift, as defined by the higher layer parameter        cyclicShift-n2 or cyclicShift-n4 for transmission comb value 2        and 4, respectively.    -   Transmission comb value as defined by the higher layer parameter        transmissionComb.    -   Transmission comb offset as defined by the higher layer        parameter combOffset-n2 or combOffset-n4 for transmission comb        value 2 or 4, respectively.    -   SRS sequence ID as defined by the higher layer parameter        sequenceId.    -   The configuration of the spatial relation between a reference RS        and the target SRS, where the higher layer parameter        spatialRelationInfo, if configured, contains the ID of the        reference RS. The reference RS can be an SS/PBCH block, CSI-RS        configured on serving cell indicated by higher layer parameter        servingCellId if present, same serving cell as the target SRS        otherwise, or an SRS configured on uplink BWP indicated by the        higher layer parameter uplinkBWP, and serving cell indicated by        the higher layer parameter servingCellId if present, same        serving cell as the target SRS otherwise.

The UE 101 may be configured by the higher layer parameterresourceMapping in SRS-Resource with an SRS resource occupying N_(s)∈{1,2, 4} adjacent symbols within the last 6 symbols of the slot, where allantenna ports of the SRS resources are mapped to each symbol of theresource. When PUSCH and SRS are transmitted in the same slot, the UE101 can only be configured to transmit SRS after the transmission of thePUSCH and the corresponding DM-RS. When the UE 101 is configured withone or more SRS resource configuration(s), and when the higher layerparameter resource Type in SRS-Resource is set to ‘periodic’, and if theUE 101 is configured with the higher layer parameter spatialRelationInfocontaining the ID of a reference ‘ssb-Index’, the UE 101 transmits thetarget SRS resource with the same spatial domain transmission filterused for the reception of the reference SS/PBCH block. If the higherlayer parameter spatialRelationInfo contains the ID of a reference‘csi-RS-Index’, the UE 101 transmits the target SRS resource with thesame spatial domain transmission filter used for the reception of thereference periodic CSI-RS or of the reference semi-persistent CSI-RS. Ifthe higher layer parameter spatialRelationInfo containing the ID of areference ‘srs’, the UE 101 transmits the target SRS resource with thesame spatial domain transmission filter used for the transmission of thereference periodic SRS.

When the UE 101 is configured with one or more SRS resourceconfiguration(s), and when the higher layer parameter resource Type inSRS-Resource is set to ‘semi-persistent’, and when the UE 101 receivesan activation command (e.g., a DCI) for an SRS resource, and when theHARQ-ACK corresponding to the PDSCH carrying the selection command istransmitted in slot n, the corresponding actions and the UE assumptionson SRS transmission corresponding to the configured SRS resource set areapplied starting from slot n+3N_(sl0t) ^(subframe,μ)+1. The activationcommand also contains spatial relation assumptions provided by a list ofreferences to reference signal IDs, one per element of the activated SRSresource set. Each ID in the list refers to a reference SS/PBCH block,NZP CSI-RS resource configured on serving cell indicated by ResourceServing Cell ID field in the activation command if present, same servingcell as the SRS resource set otherwise, or SRS resource configured onserving cell and uplink bandwidth part indicated by Resource ServingCell ID field and Resource BWP ID field in the activation command ifpresent, same serving cell and bandwidth part as the SRS resource setotherwise.

If an SRS resource in the activated resource set is configured with thehigher layer parameter spatialRelationInfo, the UE 101 assumes that theID of the reference signal in the activation command overrides the oneconfigured in spatialRelationInfo.

When the UE 101 receives a deactivation command for an activated SRSresource set, and when the HARQ-ACK corresponding to the PDSCH carryingthe selection command is transmitted in slot n, the correspondingactions and UE assumption(s) on cessation of SRS transmissioncorresponding to the deactivated SRS resource set are applied startingfrom slot n+3N_(slot) ^(subframe,μ)+1.

If the UE 101 is configured with the higher layer parameterspatialRelationInfo containing the ID of a reference ‘ssb-Index’, the UE101 transmits the target SRS resource with the same spatial domaintransmission filter used for the reception of the reference SS/PBCHblock. If the higher layer parameter spatialRelationInfo contains the IDof a reference ‘csi-RS-Index’, the UE 101 transmits the target SRSresource with the same spatial domain transmission filter used for thereception of the reference periodic CSI-RS or of the referencesemi-persistent CSI-RS. If the higher layer parameterspatialRelationInfo contains the ID of a reference ‘srs’, the UE 101transmits the target SRS resource with the same spatial domaintransmission filter used for the transmission of the reference periodicSRS or of the reference semi-persistent SRS. If the UE 101 has an activesemi-persistent SRS resource configuration and has not received adeactivation command, the semi-persistent SRS configuration isconsidered to be active in the UL BWP which is active, otherwise it isconsidered suspended.

When the UE 101 is configured with one or more SRS resourceconfiguration(s), and when the higher layer parameter resource Type inSRS-Resource is set to ‘aperiodic’, the UE 101 receives a configurationof SRS resource sets, and/or the UE 101 receives a downlink DCI, a groupcommon DCI, or an uplink DCI based command where a codepoint of the DCImay trigger one or more SRS resource set(s). For SRS in a resource setwith usage set to ‘codebook’ or ‘antennaSwitching’, the minimal timeinterval between the last symbol of the PDCCH triggering the aperiodicSRS transmission and the first symbol of SRS resource is N2, for whichthe minimal time interval in units of OFDM symbols is counted based onthe minimum subcarrier spacing between the PDCCH and the aperiodic SRS.Otherwise, the minimal time interval between the last symbol of thePDCCH triggering the aperiodic SRS transmission and the first symbol ofSRS resource is N₂+14.

If the UE 101 receives the DCI triggering aperiodic SRS in slot n, theUE 101 transmits aperiodic SRS in each of the triggered SRS resourceset(s) in slot

${\left\lfloor {n \cdot \frac{2^{\mu_{SRS}}}{2^{\mu_{PDCCH}}}} \right\rfloor + k},$where k is configured via higher layer parameter slotoffset for eachtriggered SRS resources set and is based on the subcarrier spacing ofthe triggered SRS transmission, μ_(SRS) and μ_(PDCCH) are the subcarrierspacing configurations for triggered SRS and PDCCH carrying thetriggering command respectively.

If the UE 101 is configured with the higher layer parameterspatialRelationInfo containing the ID of a reference ‘ssb-Index’, the UE101 transmits the target SRS resource with the same spatial domaintransmission filter used for the reception of the reference SS/PBCHblock. If the higher layer parameter spatialRelationInfo contains the IDof a reference ‘csi-RS-Index’, the UE 101 transmits the target SRSresource with the same spatial domain transmission filter used for thereception of the reference periodic CSI-RS or of the referencesemi-persistent CSI-RS, or of the latest reference aperiodic CSI-RS. Ifthe higher layer parameter spatialRelationInfo contains the ID of areference ‘srs’, the UE 101 transmits the target SRS resource with thesame spatial domain transmission filter used for the transmission of thereference periodic SRS or of the reference semi-persistent SRS or of thereference aperiodic SRS.

The UE 101 is not expected to be configured with different time domainbehavior for SRS resources in the same SRS resource set. The UE is alsonot expected to be configured with different time domain behaviorbetween SRS resource and associated SRS resources set. The 2-bit SRSrequest field in DCI format 0_1, 1_1 indicates the triggered SRSresource set, and the 2-bit SRS request field in DCI format 2_3indicates the triggered SRS resource set. If the UE 101 is configuredwith higher layer parameter srs-TPC-PDCCH-Group set to ‘typeB’, orindicates the SRS transmission on a set of serving cells configured byhigher layers if the UE is configured with higher layer parametersrs-TPC-PDCCH-Group set to ‘typeA’.

For PUCCH and SRS on the same carrier, the UE 101 does not transmit SRSwhen semi-persistent and periodic SRS are configured in the samesymbol(s) with PUCCH carrying only CSI report(s), or only L1-RSRPreport(s). The UE 101 does not transmit an SRS when semi-persistent orperiodic SRS is configured or aperiodic SRS is triggered to betransmitted in the same symbol(s) with PUCCH carrying HARQ-ACK and/orSR. In the case that SRS is not transmitted due to overlap with PUCCH,only the SRS symbol(s) that overlap with PUCCH symbol(s) are dropped.The PUCCH is not transmitted when aperiodic SRS is triggered to betransmitted to overlap in the same symbol with PUCCH carryingsemi-persistent/periodic CSI report(s) or semi-persistent/periodicL1-RSRP report(s) only.

In case of intra-band carrier aggregation or in inter-band CA band-bandcombination where simultaneous SRS and PUCCH/PUSCH transmissions are notallowed, the UE 101 is not expected to be configured with SRS from acarrier and PUSCH/UL DM-RS/UL PT-RS/PUCCH formats from a differentcarrier in the same symbol. In case of intra-band carrier aggregation orin inter-band CA band-band combination where simultaneous SRS and PRACHtransmissions are not allowed, the UE 101 does not transmitsimultaneously SRS resource(s) from a carrier and PRACH from a differentcarrier.

In case a SRS resource with SRS-resource Type set as ‘aperiodic’ istriggered on the OFDM symbol configured with periodic/semi-persistentSRS transmission, the UE 101 transmits the aperiodic SRS resource andnot transmit the periodic/semi-persistent SRS resource(s) overlappingwithin the symbol(s). In case a SRS resource with SRS-resource Type setas ‘semi-persistent’ is triggered on the OFDM symbol configured withperiodic SRS transmission, the UE 101 transmits the semi-persistent SRSresource and not transmit the periodic SRS resource(s) overlappingwithin the symbol(s). When the UE 101 is configured with the higherlayer parameter usage in SRS-ResourceSet set to ‘antennaSwitching,’ anda guard period of Y symbols is configured, the UE 101 uses the samepriority rules as defined above during the guard period as if SRS wasconfigured.

The CSI-RS may be used for time/frequency tracking, CSI computation,and/or L1-RSRP computation and mobility. There are two types of CSI-RSincluding a zero power (ZP) CSI-RS and a non-ZP CSI-RS (NZP CSI-RS). AnNZP CSI-RS can be configured by the NZP-CSI-RS-Resource IE in a suitableRRC message or by the CSI-RS Resource Mobility field in theCSI-RS-ResourceConfigMobility IE in a suitable RRC message. The UE 101generates the reference-signal sequence r(m) for the NZP CSI-RSaccording to equation 1.

$\begin{matrix}{{r(m)} = {{\frac{1}{\sqrt{2}}\left( {1 - {2 \cdot {c\left( {2m} \right)}}} \right)} + {j\frac{1}{\sqrt{2}}\left( {1 - {2 \cdot {c\left( {{2m} + 1} \right)}}} \right)}}} & \left\lbrack {{equation}\mspace{14mu} 1} \right\rbrack\end{matrix}$

In equation 1, c(i) is a pseudo-random sequence and a pseudo-randomsequence generator may be initialized according to equation 2.c _(init)=(2¹⁰(N _(symb) ^(slot) n _(s,f) ^(μ) +l+1)(2n _(ID)+1)+n_(ID))mod 2³¹  [equation 2]

In equation 2, at the start of each OFDM symbol where n_(s,f) ^(μ) isthe slot number within a radio frame, l is the OFDM symbol number withina slot, and n_(ID) equals the higher-layer parameter scramblingID orsequenceGenerationConfig. For each CSI-RS, the UE 101 maps the sequencer(m) to resource elements (k, l)_(p, μ).

When a zero-power CSI-RS is configured by the ZP-CSI-RS-Resource IE, theUE 101 assumes that the resource elements for that ZP CSI-RS are notused for PDSCH transmission. The UE 101 performs the samemeasurement/reception on channels/signals except PDSCH regardless ofwhether they collide with ZP CSI-RS or not. For a CSI-RS resourceassociated with a NZP-CSI-RS-ResourceSet with the higher layer parameterrepetition set to ‘on’, the UE 101 does not expect to be configured withCSI-RS over the symbols during which the UE 101 is also configured tomonitor the CORESET, while for other NZP-CSI-RS-ResourceSetconfigurations, if the UE 101 is configured with a CSI-RS resource and asearch space set associated with a CORESET in the same OFDM symbol(s),the UE 101 may assume that the CSI-RS and a PDCCH DM-RS transmitted inall the search space sets associated with CORESET are quasi co-locatedwith ‘QCL-TypeD’, if ‘QCL-TypeD’ is applicable. This also applies to thecase when CSI-RS and the CORESET are in different intra-band componentcarriers, if ‘QCL-TypeD’ is applicable. Furthermore, the UE s101 doesnot expect to be configured with the CSI-RS in PRBs that overlap thoseof the CORESET in the OFDM symbols occupied by the search space set(s).

The UE 101 is not expected to receive CSI-RS and aSystemInformationBlockType1 message in the overlapping PRBs in the OFDMsymbols where SystemInformationBlockType1 is transmitted. If the UE 101is configured with DRX, the most recent CSI measurement occasion occursin DRX active time for CSI to be reported. The time and frequencyresources that can be used by the UE 101 to report CSI are controlled bythe RAN node 111 (e.g., a gNB). A CSI may include a Channel QualityIndicator (CQI), precoding matrix indicator (PMI), CSI-RS resourceindicator (CRI), SS/PBCH Block Resource indicator (SSBRI), layerindicator (LI), rank indicator (RI), and/or L1-RSRP. For CQI, PMI, CRI,SSBRI, LI, RI, L1-RSRP, the UE 101 may be configured by higher layerswith N≥1 CSI-ReportConfig Reporting Settings, M≥1 CSI-ResourceConfigResource Settings, and one or two list(s) of trigger states (given bythe higher layer parameters CSI-AperiodicTriggerStateList andCSI-SemiPersistentOnPUSCH-TriggerStateList). Each trigger state inCSI-AperiodicTriggerStateList contains a list of associatedCSI-ReportConfigs indicating the Resource Set IDs for channel andoptionally for interference. Each trigger state inCSI-SemiPersistentOnPUSCH-TriggerStateList contains one associatedCSI-ReportConfig.

The UE 101 can be configured with one or more NZP CSI-RS resource setconfiguration(s) as indicated by the higher layer parametersCSI-ResourceConfig, and NZP-CSI-RS-ResourceSet. Each NZP CSI-RS resourceset consists of K≥1 NZP CSI-RS resource(s). The following parameters forwhich the UE 101 assumes non-zero transmission power for CSI-RS resourceare configured via the higher layer parameter NZP-CSI-RS-Resource,CSI-ResourceConfig and NZP-CSI-RS-ResourceSet for each CSI-RS resourceconfiguration:

-   -   nzp-CSI-RS-ResourceId determines CSI-RS resource configuration        identity.    -   periodicityAndOffset defines the CSI-RS periodicity and slot        offset for periodic/semi-persistent CSI-RS. All the CSI-RS        resources within one set are configured with the same        periodicity, while the slot offset can be same or different for        different CSI-RS resources.    -   resourceMapping defines the number of ports, CDM-type, and OFDM        symbol and subcarrier occupancy of the CSI-RS resource within a        slot.    -   nrofPorts in resourceMapping defines the number of CSI-RS ports.    -   density in resourceMapping defines CSI-RS frequency density of        each CSI-RS port per PRB, and CSI-RS PRB offset in case of the        density value of ½. For density ½, the odd/even PRB allocation        indicated in density is with respect to the common resource        block grid.    -   cdm-Type in resourceMapping defines CDM values and pattern.    -   powerControlOffset: which is the assumed ratio of PDSCH EPRE to        NZP CSI-RS EPRE when UE derives CSI feedback and takes values in        the range of [−8, 15] dB with 1 dB step size.    -   powerControlOffsetSS: which is the assumed ratio of NZP CSI-RS        EPRE to SS/PBCH block EPRE.    -   scramblingID defines scrambling ID of CSI-RS with length of 10        bits.    -   bwp-Id in CSI-ResourceConfig defines which bandwidth part the        configured CSI-RS is located in.    -   repetition in NZP-CSI-RS-ResourceSet is associated with a CSI-RS        resource set and defines whether UE can assume the CSI-RS        resources within the NZP CSI-RS Resource Set are transmitted        with the same downlink spatial domain transmission filter or        not. and can be configured only when the higher layer parameter        reportQuantity associated with all the reporting settings linked        with the CSI-RS resource set is set to ‘cri-RSRP’ or ‘none’.    -   qcl-InfoPeriodicCSI-RS contains a reference to a TCI-State        indicating QCL source RS(s) and QCL type(s). If the TCI-State is        configured with a reference to an RS with ‘QCL-TypeD’        association, that RS may be an SS/PBCH block located in the same        or different CC/DL BWP or a CSI-RS resource configured as        periodic located in the same or different CC/DL BWP.    -   trs-Info in NZP-CSI-RS-ResourceSet is associated with a CSI-RS        resource set and for which the UE can assume that the antenna        port with the same port index of the configured NZP CSI-RS        resources in the NZP-CSI-RS-ResourceSet is the same and can be        configured when reporting setting is not configured or when the        higher layer parameter reportQuantity associated with all the        reporting settings linked with the CSI-RS resource set is set to        ‘none’.

All CSI-RS resources within one set are configured with same density andsame nrofPorts, except for the NZP CSI-RS resources used forinterference measurement. The bandwidth and initial common resourceblock (CRB) index of a CSI-RS resource within a BWP, are determinedbased on the higher layer parameters nrofRBs and startingRB,respectively, within the CSI-FrequencyOccupation IE configured by thehigher layer parameter freqBand within the CSI-RS-ResourceMapping IE.Both nrofRBs and startingRB are configured as integer multiples of 4RBs, and the reference point for startingRB is CRB 0 on the commonresource block grid. If startingRB<N_(BWP) ^(start), the UE shall assumethat the initial CRB index of the CSI-RS resource isN_(initial RB)=N_(BWP) ^(start), otherwise N_(initial RB)=startingRB. IfnrofRBs>N_(BWP) ^(size)+N_(BWP) ^(start)−N_(initial RB), the UE shallassume that the bandwidth of the CSI-RS resource is N_(CSI-RS)^(BW)=N_(BWP) ^(size)+N_(BWP) ^(start)−N_(initial RB), otherwiseN_(CSI-RS) ^(BW)=nrofRBs. In all cases, the UE shall expect thatN_(CSI-RS) ^(BW)≥min(24, N_(BWP) ^(size)).

As mentioned previously, there may be N CSI-RS resources in one CSI-RSresource set (where N is a number), and the UE 101 may be configuredwith M CSI-RS resource set. One CSI-RS resource set may include thefollowing configurations: TRS-Info={ON/OFF} and Repetition={ON/OFF}.According to various embodiments, if TRS-Info is “ON”, the antenna portsof the CSI-RS resources in a resource set can be assumed to be the same;otherwise, they cannot be assumed to be the same. In some embodiments,the TRS-info cannot be configured to “OFF.” In various embodiments, ifRepetition is “ON”, the CSI-RS resources in a resource set can beassumed to be spatially quasi co-located (QCLed) and/or all share thesame transmitting (Tx) beams; otherwise, those CSI-RS resources cannotbe assumed to be QCLed. In other words, only one of the TRS-Infoparameter or the Repetition parameter can be configured by theNZP-CSI-RS-ResourceSet, and the case to configure Repetition=OFF andTRS-Info for a CSI-RS resource set should not be allowed. It should benoted that when the Tx beams are the same or shared, such Tx beams alsouse a same spatial domain transmission filter.

For each CSI-RS resource, there can be the following configurations toconfigure its Tx beam: QCL-Info-PeriodicCSI-RS andQCL-Info-aPeriodicReportingTrigger. It should be noted that theQCL-Info-aPeriodicReportingTrigger may also be referred to simply asqcl-Info or the like. The QCL-Info-PeriodicCSI-RS can be used toindicate the Tx beam for periodic CSI-RS resources, andQCL-Info-aPeriodicReportingTrigger can be used to indicate the Tx beamfor aperiodic CSI-RS resources. Then there may be some confliction forthe control signaling above.

In various embodiments, the UE is not be expected to be configured withboth TRS-Info and Repetition in a CSI-RS resource set. Alternatively,the UE 101 is not be expected to be configured with TRS-Info=“ON” andRepetition=“OFF.” Otherwise, the UE 101 may not identify whether thebeams can be assumed to be the same for all of the CSI-RS resources. Inother embodiments, when TRS-INFO=“ON” or Repetition=“ON” in a CSI-RSresource set, the UE 101 is not expected to be configured with adifferent value of QCL-Info-PeriodicCSI-RS or differentQCL-Info-aPeriodicReportingTrigger for the CSI-RS resources in theresource set. Alternatively, when TRS-INFO=“ON” or Repetition=“ON”, theUE 101 is not expected to be configured with QCL-Info-PeriodicCSI-RS orQCL-Info-aPeriodicReportingTrigger.

In other embodiments, the number of antenna ports for the CSI-RS whichis associated with one SRS resource set for non-codebook basedtransmission may be no less than the maximum transmitted layers fornon-codebook based transmission. Alternatively, the maximum number oftransmitted layers for a non-codebook based transmission may be themin{N_(ap), N_(layer), N_(Resource)} where N_(ap) indicates the numberof antenna ports for associated CSI-RS, N_(layer) indicates the maximumreported transmitted layers and N_(Resource) indicates number ofconfigured SRS resources for non-codebook based transmission. Further,for the CSI-RS associated with one SRS resource set, if it is triggeredin an aperiodic manner, its reportQuantity may be configured to“No-report”, which indicates that the UE 101 need not report any CSI butmay just use it for uplink measurement purposes. Alternatively, resourceallocation may be based on 0 RB allocation so that the UE may skip CSIreporting altogether.

For CSI-RS for tracking, when the UE 101 in RRC connected mode isexpected to receive the higher layer UE specific configuration of aNZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info.For a NZP-CSI-RS-ResourceSet configured with the higher layer parametertrs-Info, the UE 101 assumes the antenna port with the same port indexof the configured NZP CSI-RS resources in the NZP-CSI-RS-ResourceSet isthe same. For frequency range 1, the UE may be configured with one ormore NZP CSI-RS set(s), where a NZP-CSI-RS-ResourceSet consists of fourperiodic NZP CSI-RS resources in two consecutive slots with two periodicNZP CSI-RS resources in each slot. For frequency range 2 the UE 101 maybe configured with one or more NZP CSI-RS set(s), where aNZP-CSI-RS-ResourceSet consists of two periodic CSI-RS resources in oneslot or with a NZP-CSI-RS-ResourceSet of four periodic NZP CSI-RSresources in two consecutive slots with two periodic NZP CSI-RSresources in each slot.

When the UE 101 is configured with NZP-CSI-RS-ResourceSet(s) configuredwith higher layer parameter trs-Info may have the CSI-RS resourcesconfigured as:

-   -   Periodic, with the CSI-RS resources in the        NZP-CSI-RS-ResourceSet configured with same periodicity,        bandwidth and subcarrier location; and/or    -   Periodic CSI-RS resource in one set and aperiodic CSI-RS        resources in a second set, with the aperiodic CSI-RS and        periodic CSI-RS resource having the same bandwidth (with same RB        location) and the aperiodic CSI-RS being ‘QCL-Type-A’ and        ‘QCL-TypeD’, where applicable, with the periodic CSI-RS        resources. For frequency range 2, the UE 101 does not expect        that the scheduling offset between the last symbol of the PDCCH        carrying the triggering DCI and the first symbol of the        aperiodic CSI-RS resources is smaller than the UE reported        ThresholdSched-Offset. The UE 101 expects that the periodic        CSI-RS resource set and aperiodic CSI-RS resource set are        configured with the same number of CSI-RS resources and with the        same number of CSI-RS resources in a slot. For the aperiodic        CSI-RS resource set if triggered, and if the associated periodic        CSI-RS resource set is configured with four periodic CSI-RS        resources with two consecutive slots with two periodic CSI-RS        resources in each slot, the higher layer parameter aperiodic        TriggeringOffset indicates the triggering offset for the first        slot for the first two CSI-RS resources in the set.

The UE 101 does not expect to be configured with a CSI-ReportConfig thatis linked to a CSI-ResourceConfig containing an NZP-CSI-RS-ResourceSetconfigured with trs-Info and with the CSI-ReportConfig configured withthe higher layer parameter timeRestrictionForChannelMeasurements set to‘configured’. The UE 101 does not expect to be configured with aCSI-ReportConfig with the higher layer parameter reportQuantity set toother than ‘none’ for aperiodic NZP CSI-RS resource set configured withtrs-Info. The UE 101 does not expect to be configured with aCSI-ReportConfig for periodic NZP CSI-RS resource set configured withtrs-Info. The UE 101 does not expect to be configured with aNZP-CSI-RS-ResourceSet configured both with trs-Info and repetition.

Each CSI-RS resource is configured by the higher layer parameterNZP-CSI-RS-Resource with the following restrictions:

-   -   the time-domain locations of the two CSI-RS resources in a slot,        or of the four CSI-RS resources in two consecutive slots (which        are the same across two consecutive slots), as defined by higher        layer parameter CSI-RS-resourceMapping, is given by one of        -   l∈{4,8}, l∈{5,9}, or l∈{6,10} for frequency range 1 and            frequency range 2,        -   l∈{0,4}, l∈{1,5}, l∈{2,6}, l∈{3,7}, l∈{7,11}, l∈{8,12} or            l∈{9,13} for frequency range 2.    -   a single port CSI-RS resource with density ρ=3 and higher layer        parameter density configured by CSI-RS-ResourceMapping.    -   the bandwidth of the CSI-RS resource, as given by the higher        layer parameter freqBand configured by CSI-RS-ResourceMapping,        is the minimum of 52 and N_(RB) ^(BWP,i) resource blocks, or is        equal to N_(RB) ^(BWP,i) resource blocks.    -   the UE 101 is not expected to be configured with the periodicity        of 2^(μ)×10 slots if the bandwidth of CSI-RS resource is larger        than 52 resource blocks.    -   the periodicity and slot offset for periodic NZP CSI-RS        resources, as given by the higher layer parameter        periodicityAndOffset configured by NZP-CSI-RS-Resource, is one        of 2^(μ)X_(p) slots where X_(p)=10, 20, 40, or 80.    -   same powerControlOffset and powerControlOffsetSS given by        NZP-CSI-RS-Resource value across all resources.

For CSI-RS for L1-RSRP computation, if the UE 101 is configured with aNZP-CSI-RS-ResourceSet configured with the higher layer parameterrepetition set to ‘on’, the UE 101 may assume that the CSI-RS resources,within the NZP-CSI-RS-ResourceSet are transmitted with the same downlinkspatial domain transmission filter, where the CSI-RS resources in theNZP-CSI-RS-ResourceSet are transmitted in different OFDM symbols. Ifrepetition is set to ‘off’, the UE shall not assume that the CSI-RSresources within the NZP-CSI-RS-ResourceSet are transmitted with thesame downlink spatial domain transmission filter.

If the UE is configured with a CSI-ReportConfig with reportQuantity setto “cri-RSRP”, or “none” and if the CSI-ResourceConfig for channelmeasurement (higher layer parameter resourcesForChannelMeasurement)contains a NZP-CSI-RS-ResourceSet that is configured with the higherlayer parameter repetition and without the higher layer parametertrs-Info, the UE can only be configured with the same number (1 or 2) ofports with the higher layer parameter nrofPorts for all CSI-RS resourceswithin the set. If the UE is configured with the CSI-RS resource in thesame OFDM symbol(s) as an SS/PBCH block, the UE may assume that theCSI-RS and the SS/PBCH block are quasi co-located with ‘QCL-TypeD’ if‘QCL-TypeD’ is applicable. Furthermore, the UE shall not expect to beconfigured with the CSI-RS in PRBs that overlap with those of theSS/PBCH block, and the UE shall expect that the same subcarrier spacingis used for both the CSI-RS and the SS/PBCH block.

For CSI-RS for Mobility, if the UE 101 is configured with the higherlayer parameter CSI-RS-Resource-Mobility and the higher layer parameterassociatedSSB is not configured, the UE 101 performs measurements basedon CSI-RS-Resource-Mobility and the UE 101 may base the timing of theCSI-RS resource on the timing of the serving cell. If the UE 101 isconfigured with the higher layer parameters CSI-RS-Resource-Mobility andassociatedSSB, the UE may base the timing of the CSI-RS resource on thetiming of the cell given by the cellId of the CSI-RS resourceconfiguration. Additionally, for a given CSI-RS resource, if theassociated SS/PBCH block is configured but not detected by the UE, theUE is not required to monitor the corresponding CSI-RS resource. Thehigher layer parameter isQuasiColocated indicates whether the associatedSS/PBCH block given by the associatedSSB and the CSI-RS resource(s) arequasi co-located with respect to, for example, ‘QCL-TypeD’. If the UE101 is configured with the higher layer parameterCSI-RS-Resource-Mobility and with periodicity greater than 10 ms inpaired spectrum, the UE may assume the absolute value of the timedifference between radio frame i between any two cells, listed in theconfiguration with the higher layer parameter CSI-RS-CellMobility andwith same refFreqCSI-RS, is less than 153600 T_(s). If the UE 101 isconfigured with DRX, the UE is not required to perform measurement ofCSI-RS resources other than during the active time for measurementsbased on CSI-RS-Resource-Mobility. If the UE 101 is configured with DRXand DRX cycle in use is larger than 80 ms, the UE may not expect CSI-RSresources are available other than during the active time formeasurements based on CSI-RS-Resource-Mobility. Otherwise, the UE mayassume CSI-RS are available for measurements based onCSI-RS-Resource-Mobility.

When the UE 101 is configured with the higher layer parametersCSI-RS-Resource-Mobility, the UE 101 may expect to be configured with nomore than 96 CSI-RS resources when all CSI-RS resources per frequencylayer have been configured with associatedSSB, or with no more than 64CSI-RS resources per frequency layer when all CSI-RS resources have beenconfigured without associatedSSB or when only some of the CSI-RSresources have been configured with associatedSSB. For frequency range1, the associatedSSB is optionally present for each CSI-RS resource. Forfrequency range 2 the associatedSSB is either present for all configuredCSI-RS resources or not present for any configured CSI-RS resources-perfrequency layer. For any CSI-RS resource configuration, the UE shallassume that the value for parameter cdm-Type is ‘No CDM’, and there isonly one antenna port.

For CSI-RS resource sets associated with resource settings configuredwith the higher layer parameter resource Type set to ‘aperiodic’,‘periodic’, or ‘semi-persistent’, trigger states for reportingsetting(s) (configured with the higher layer parameter reportConfigTypeset to ‘aperiodic’) and/or resource setting for channel and/orinterference measurement on one or more component carriers areconfigured using the higher layer parameter CSI-AperiodicTriggerStateList. For aperiodic CSI report triggering, a single set ofCSI triggering states are higher layer configured, wherein the CSItriggering states can be associated with any candidate DL BWP. The UE101 is not expected to receive more than one DCI with non-zero CSIrequest per slot. The UE 101 is not expected to be configured withdifferent TCI-StateId's for the same aperiodic CSI-RS resource IDconfigured in multiple aperiodic CSI-RS resource sets with the sametriggering offset in the same aperiodic trigger state. The UE 101 is notexpected to receive more than one aperiodic CSI report request fortransmission in a given slot. The UE 101 is not expected to be triggeredwith a CSI report for a non-active DL BWP.

A trigger state is initiated using the CSI request field in DCI. Whenall the bits of CSI request field in DCI are set to zero, no CSI isrequested. When the number of configured CSI triggering states inCSI-AperiodicTriggerStateList is greater than 2^(N) ^(TS) −1, whereN_(TS) is the number of bits in the DCI CSI request field, the UE 101receives a selection command used to map up to 2^(N) ^(TS) −1 triggerstates to the codepoints of the CSI request field in DCI. N_(TS) isconfigured by the higher layer parameter reportTriggerSize whereN_(TS)∈{0,1,2,3,4,5,6}. When the HARQ/ACK corresponding to the PDSCHcarrying the selection command is transmitted in the slot n, thecorresponding action and UE assumption(s) on the mapping of the selectedCSI trigger state(s) to the codepoint(s) of DCI CSI request field shallbe applied starting from slot n+3N_(slot) ^(subframe,μ)+1. When thenumber of CSI triggering states in CSI-AperiodicTriggerStateList is lessthan or equal to 2^(N) ^(TS) −1, the CSI request field in DCI directlyindicates the triggering state. For each aperiodic CSI-RS resource in aCSI-RS resource set associated with each CSI triggering state, the UE101 identifies the QCL configuration of QCL RS resource(s) and QCLtype(s) through higher layer signaling of qcl-info, which contains alist of references to TCI-State's for the aperiodic CSI-RS resourcesassociated with the CSI triggering state. If a State referred to in thelist is configured with a reference to an RS associated with‘QCL-TypeD’, that RS may be an SS/PBCH block located in the same ordifferent CC/DL BWP or a CSI-RS resource configured as periodic orsemi-persistent located in the same or different CC/DL BWP.

If the scheduling offset between the last symbol of the PDCCH carryingthe triggering DCI and the first symbol of the aperiodic CSI-RSresources in a NZP-CSI-RS-ResourceSet configured without higher layerparameter trs-Info and without the higher layer parameter repetition issmaller than the UE reported threshold beamSwitchTiming when thereported value is one of the values of {14, 28, 48}. If there is anyother DL signal with an indicated TCI state in the same symbols as theCSI-RS, the UE 101 applies the QCL assumption of the other DL signalalso when receiving the aperiodic CSI-RS. The other DL signal refers toPDSCH scheduled with offset larger than or equal to the thresholdtimeDurationForQCL aperiodic CSI-RS scheduled with offset larger than orequal to the UE reported threshold beamSwitchTiming when the reportedvalues is one of the values {14,28,48}, periodic CSI-RS, semi-persistentCSI-RS. If the scheduling offset between the last symbol of the PDCCHcarrying the triggering DCI and the first symbol of the aperiodic CSI-RSresources is equal to or greater than the UE reported thresholdbeamSwitchTiming when the reported value is one of the values of{14,28,48}, the UE 101 is expected to apply the QCL assumptions in theindicated TCI states for the aperiodic CSI-RS resources in the CSItriggering state indicated by the CSI trigger field in DCI.

A non-zero codepoint of the CSI request field in the DCI is mapped to aCSI triggering state according to the order of the associated positionsof the up to 2^(N) ^(TS) −1 trigger states in CSI-AperiodicTriggerStateList with codepoint ‘1’ mapped to the triggering state inthe first position. When the UE 101 is configured with the higher layerparameter CSI-AperiodicTriggerStateList, and if a Resource Settinglinked to a CSI-ReportConfig has multiple aperiodic resource sets, onlyone of the aperiodic CSI-RS resource sets from the Resource Setting isassociated with the trigger state, and the UE 101 is higher layerconfigured per trigger state per Resource Setting to select the oneCSI-IM/NZP CSI-RS resource set from the Resource Setting.

When aperiodic CSI-RS is used with aperiodic reporting, the CSI-RSoffset is configured per resource set by the higher layer parameteraperiodicTriggeringOffset. The CSI-RS triggering offset has the range of0 to 4 slots. If all the associated trigger states do not have thehigher layer parameter qcl-Type set to ‘QCL-TypeD’ in the correspondingTCI states, the CSI-RS triggering offset is fixed to zero. The aperiodictriggering offset of the CSI-IM follows offset of the associated NZPCSI-RS for channel measurement.

The UE 101 does not expect that aperiodic CSI-RS is transmitted beforethe OFDM symbol(s) carrying its triggering DCI. If interferencemeasurement is performed on aperiodic NZP CSI-RS, the UE 101 is notexpected to be configured with a different aperiodic triggering offsetof the NZP CSI-RS for interference measurement from the associated NZPCSI-RS for channel measurement. If the UE 101 is configured with asingle carrier for uplink, the UE 101 is not expected to transmit morethan one aperiodic CSI report triggered by different DCIs on overlappingOFDM symbols.

For semi-persistent reporting on PUSCH, a set of trigger states arehigher layer configured by CSI-SemiPersistentOnPUSCH-TriggerStateList,where the CSI request field in DCI scrambled with SP-CSI-RNTI activatesone of the trigger states. For semi-persistent reporting on PUCCH, thePUCCH resource used for transmitting the CSI report are configured byreportConfigType. A UE is not expected to receive a DCI scrambled withSP-CSI-RNTI activating one semi-persistent CSI report with the sameCSI-ReportConfigId as in a semi-persistent CSI report which is activatedby a previously received DCI scrambled with SP-CSI-RNTI.

Semi-persistent reporting on PUCCH is activated by an activation command(e.g., DCI), which selects one of the semi-persistent Reporting Settingsfor use by the UE 101 on the PUCCH. When the HARQ-ACK corresponding tothe PDSCH carrying the activation command is transmitted in slot n, theindicated semi-persistent Reporting Setting should be applied startingfrom slot n+3N_(slot) ^(subframe,μ)+1.

When the UE 101 is configured with CSI resource setting(s) where thehigher layer parameter resourceType set to ‘semiPersistent’, and whenthe UE 101 receives an activation command (e.g., DCI) for CSI-RSresource set(s) for channel measurement and CSI-IM/NZP CSI-RS resourceset(s) for interference measurement associated with configured CSIresource setting(s), and when the HARQ-ACK corresponding to the PDSCHcarrying the selection command is transmitted in slot n, thecorresponding actions and the UE assumptions (including QCL assumptionsprovided by a list of reference to TCI-State's, one per activatedresource) on CSI-RS/CSI-IM transmission corresponding to the configuredCSI-RS/CSI-IM resource configuration(s) shall be applied starting fromslot n+3N_(slot) ^(subframe,μ)+1. If a TCI-State referred to in the listis configured with a reference to an RS associated with ‘QCL-TypeD’,that RS can be an SS/PBCH block, periodic or semi-persistent CSI-RSlocated in same or different CC/DL BWP.

When the UE 101 is configured with CSI resource setting(s) where thehigher layer parameter resourceType set to ‘semiPersistent’, and whenthe UE 101 receives a deactivation command (e.g., DCI) for activatedCSI-RS/CSI-IM resource set(s) associated with configured CSI resourcesetting(s), and when the HARQ-ACK corresponding to the PDSCH carryingthe selection command is transmitted in slot n, the correspondingactions and UE assumption(s) on cessation of CSI-RS/CSI-IM transmissioncorresponding to the deactivated CSI-RS/CSI-IM resource set(s) shallapply starting from slot n+3N_(slot) ^(subframe,μ)+1.

A codepoint of the CSI request field in the DCI is mapped to a SP-CSItriggering state according to the order of the positions of theconfigured trigger states in CSI-SemiPersistentOnPUSCH-TriggerStateList,with codepoint ‘0’ mapped to the triggering state in the first position.A UE validates, for semi-persistent CSI activation or release, a DLsemi-persistent assignment PDCCH on a DCI only if the followingconditions are met: the CRC parity bits of the DCI format are scrambledwith a SP-CSI-RNTI provided by higher layer parameter sp-csi-RNTI; andspecial fields for the DCI format are set.

If validation is achieved, the UE 101 considers the information in theDCI format as a valid activation or valid release of semi-persistent CSItransmission on PUSCH, and the UE 101 activates or deactivates a CSIReporting Setting indicated by CSI request field in the DCI. Ifvalidation is not achieved, the UE considers the DCI format as havingbeen detected with a non-matching CRC.

If the UE 101 has an active semi-persistent CSI-RS/CSI-IM resourceconfiguration, or an active semi-persistent ZP CSI-RS resource setconfiguration, and has not received a deactivation command, theactivated semi-persistent CSI-RS/CSI-IM resource set or the activatedsemi-persistent ZP CSI-RS resource set configurations are considered tobe active when the corresponding DL BWP is active, otherwise they areconsidered suspended. If the UE 101 is configured with carrierdeactivation, the following configurations in the carrier in activatedstate would also be deactivated and need re-activation configuration(s):semi-persistent CSI-RS/CSI-IM resource, semi-persistent CSI reporting onPUCCH, semi-persistent SRS, semi-persistent ZP CSI-RS resource set

Referring back to FIG. 1, the RAN nodes 111 may be configured tocommunicate with one another via interface 112. In embodiments where thesystem 100 is an LTE system (e.g., when CN 120 is an EPC 520 as in FIG.5), the interface 112 may be an X2 interface 112. The X2 interface maybe defined between two or more RAN nodes 111 (e.g., two or more eNBs andthe like) that connect to EPC 120, and/or between two eNBs connecting toEPC 120. In some implementations, the X2 interface may include an X2user plane interface (X2-U) and an X2 control plane interface (X2-C).The X2-U may provide flow control mechanisms for user data packetstransferred over the X2 interface, and may be used to communicateinformation about the delivery of user data between eNBs. For example,the X2-U may provide specific sequence number information for user datatransferred from a MeNB to an SeNB; information about successful insequence delivery of PDCP PDUs to a UE 101 from an SeNB for user data;information of PDCP PDUs that were not delivered to a UE 101;information about a current minimum desired buffer size at the SeNB fortransmitting to the UE user data; and the like. The X2-C may provideintra-LTE access mobility functionality, including context transfersfrom source to target eNBs, user plane transport control, etc.; loadmanagement functionality; as well as inter-cell interferencecoordination functionality.

In embodiments where the system 100 is a 5G or NR system (e.g., when CN120 is an 5GC 620 as in FIG. 6), the interface 112 may be an Xninterface 112. The Xn interface is defined between two or more RAN nodes111 (e.g., two or more gNBs and the like) that connect to 5GC 120,between a RAN node 111 (e.g., a gNB) connecting to 5GC 120 and an eNB,and/or between two eNBs connecting to 5GC 120. In some implementations,the Xn interface may include an Xn user plane (Xn-U) interface and an Xncontrol plane (Xn-C) interface. The Xn-U may provide non-guaranteeddelivery of user plane PDUs and support/provide data forwarding and flowcontrol functionality. The Xn-C may provide management and errorhandling functionality, functionality to manage the Xn-C interface;mobility support for UE 101 in a connected mode (e.g., CM-CONNECTED)including functionality to manage the UE mobility for connected modebetween one or more RAN nodes 111. The mobility support may includecontext transfer from an old (source) serving RAN node 111 to new(target) serving RAN node 111; and control of user plane tunnels betweenold (source) serving RAN node 111 to new (target) serving RAN node 111.A protocol stack of the Xn-U may include a transport network layer builton Internet Protocol (IP) transport layer, and a GTP-U layer on top of aUDP and/or IP layer(s) to carry user plane PDUs. The Xn-C protocol stackmay include an application layer signaling protocol (referred to as XnApplication Protocol (Xn-AP)) and a transport network layer that isbuilt on SCTP. The SCTP may be on top of an IP layer, and may providethe guaranteed delivery of application layer messages. In the transportIP layer, point-to-point transmission is used to deliver the signalingPDUs. In other implementations, the Xn-U protocol stack and/or the Xn-Cprotocol stack may be same or similar to the user plane and/or controlplane protocol stack(s) shown and described herein.

The RAN 110 is shown to be communicatively coupled to a core network—inthis embodiment, core network (CN) 120. The CN 120 may comprise aplurality of network elements 122, which are configured to offer variousdata and telecommunications services to customers/subscribers (e.g.,users of UEs 101) who are connected to the CN 120 via the RAN 110. Thecomponents of the CN 120 may be implemented in one physical node orseparate physical nodes including components to read and executeinstructions from a machine-readable or computer-readable medium (e.g.,a non-transitory machine-readable storage medium). In some embodiments,NFV may be utilized to virtualize any or all of the above-describednetwork node functions via executable instructions stored in one or morecomputer-readable storage mediums (described in further detail below). Alogical instantiation of the CN 120 may be referred to as a networkslice, and a logical instantiation of a portion of the CN 120 may bereferred to as a network sub-slice. NFV architectures andinfrastructures may be used to virtualize one or more network functions,alternatively performed by proprietary hardware, onto physical resourcescomprising a combination of industry-standard server hardware, storagehardware, or switches. In other words, NFV systems can be used toexecute virtual or reconfigurable implementations of one or more EPCcomponents/functions.

The CN 120 includes one or more servers 122, which may implement variouscore network elements or application functions (AFs) such as thosediscussed herein. The CN 120 is shown to be communicatively coupled toapplication servers 130 via an IP communications interface 125. Theapplication server(s) 130 comprise one or more physical and/orvirtualized systems for providing functionality (or services) to one ormore clients (e.g., UEs 101) over a network (e.g., network 150). Theserver(s) 130 may include various computer devices with rack computingarchitecture component(s), tower computing architecture component(s),blade computing architecture component(s), and/or the like. Theserver(s) 130 may represent a cluster of servers, a server farm, a cloudcomputing service, or other grouping or pool of servers, which may belocated in one or more datacenters. The server(s) 130 may also beconnected to, or otherwise associated with one or more data storagedevices (not shown). Moreover, the server(s) 130 may include anoperating system (OS) that provides executable program instructions forthe general administration and operation of the individual servercomputer devices, and may include a computer-readable medium storinginstructions that, when executed by a processor of the servers, mayallow the servers to perform their intended functions. Suitableimplementations for the OS and general functionality of servers areknown or commercially available, and are readily implemented by personshaving ordinary skill in the art. Generally, the server(s) 130 offerapplications or services that use IP/network resources. As examples, theserver(s) 130 may provide traffic management services, cloud analytics,content streaming services, immersive gaming experiences, socialnetworking and/or microblogging services, and/or other like services. Inaddition, the various services provided by the server(s) 130 may includeinitiating and controlling software and/or firmware updates forapplications or individual components implemented by the UEs 101. Theserver(s) 130 can also be configured to support one or morecommunication services (e.g., Voice-over-Internet Protocol (VoIP)sessions, PTT sessions, group communication sessions, social networkingservices, etc.) for the UEs 101 via the CN 120.

In embodiments, the CN 120 may be a 5GC (referred to as “5GC 120” or thelike), and the RAN 110 may be connected with the CN 120 via an NGinterface 113. In embodiments, the NG interface 113 may be split intotwo parts, an NG user plane (NG-U) interface 114, which carries trafficdata between the RAN nodes 111 and a UPF, and the S1 control plane(NG-C) interface 115, which is a signaling interface between the RANnodes 111 and AMFs. Embodiments where the CN 120 is a 5GC 120 arediscussed in more detail with regard to FIG. 6.

In embodiments, the CN 120 may be a 5G CN (referred to as “5GC 120” orthe like), while in other embodiments, the CN 120 may be an EPC). WhereCN 120 is an EPC (referred to as “EPC 120” or the like), the RAN 110 maybe connected with the CN 120 via an S1 interface 113. In embodiments,the S1 interface 113 may be split into two parts, an S1 user plane(S1-U) interface 114, which carries traffic data between the RAN nodes111 and the S-GW, and the S1-MME interface 115, which is a signalinginterface between the RAN nodes 111 and MMES. An example architecturewherein the CN 120 is an EPC 120 is shown by FIG. 5.

FIG. 5 illustrates an example architecture of a system 200 including afirst CN 520, in accordance with various embodiments. In this example,system 200 may implement the LTE standard wherein the CN 520 is an EPC520 that corresponds with CN 120 of FIG. 1. Additionally, the UE 501 maybe the same or similar as the UEs 101 of FIG. 1, and the E-UTRAN 510 maybe a RAN that is the same or similar to the RAN 110 of FIG. 1, and whichmay include RAN nodes 111 discussed previously. The CN 520 may compriseMMEs 521, an S-GW 522, a P-GW 523, a HSS 524, and a SGSN 525.

The MMEs 521 may be similar in function to the control plane of legacySGSN, and may implement MM functions to keep track of the currentlocation of a UE 501. The MMEs 521 may perform various MM procedures tomanage mobility aspects in access such as gateway selection and trackingarea list management. MM (also referred to as “EPS MM” or “EMM” inE-UTRAN systems) refers to all applicable procedures, methods, datastorage, etc. that are used to maintain knowledge about a presentlocation of the UE 501, provide user identity confidentiality, and/orperform other like services to users/subscribers. Each UE 501 and theMME 521 may include an MM or EMM sublayer, and an MM context may beestablished in the UE 501 and the MME 521 when an attach procedure issuccessfully completed. The MM context may be a data structure ordatabase object that stores MM-related information of the UE 501. TheMMEs 521 may be coupled with the HSS 524 via an S6a reference point,coupled with the SGSN 525 via an S3 reference point, and coupled withthe S-GW 522 via an S11 reference point.

The SGSN 525 may be a node that serves the UE 501 by tracking thelocation of an individual UE 501 and performing security functions. Inaddition, the SGSN 525 may perform Inter-EPC node signaling for mobilitybetween 2G/3G and E-UTRAN 3GPP access networks; PDN and S-GW selectionas specified by the MMEs 521; handling of UE 501 time zone functions asspecified by the MMEs 521; and MME selection for handovers to E-UTRAN3GPP access network. The S3 reference point between the MMEs 521 and theSGSN 525 may enable user and bearer information exchange for inter-3GPPaccess network mobility in idle and/or active states.

The HSS 524 may comprise a database for network users, includingsubscription-related information to support the network entities'handling of communication sessions. The EPC 520 may comprise one orseveral HSSs 524, depending on the number of mobile subscribers, on thecapacity of the equipment, on the organization of the network, etc. Forexample, the HSS 524 can provide support for routing/roaming,authentication, authorization, naming/addressing resolution, locationdependencies, etc. An S6a reference point between the HSS 524 and theMMEs 521 may enable transfer of subscription and authentication data forauthenticating/authorizing user access to the EPC 520 between HSS 524and the MMEs 521.

The S-GW 522 may terminate the S1 interface 113 (“S1-U” in FIG. 5)toward the RAN 510, and routes data packets between the RAN 510 and theEPC 520. In addition, the S-GW 522 may be a local mobility anchor pointfor inter-RAN node handovers and also may provide an anchor forinter-3GPP mobility. Other responsibilities may include lawfulintercept, charging, and some policy enforcement. The S11 referencepoint between the S-GW 522 and the MMEs 521 may provide a control planebetween the MMEs 521 and the S-GW 522. The S-GW 522 may be coupled withthe P-GW 523 via an S5 reference point.

The P-GW 523 may terminate an SGi interface toward a PDN 530. The P-GW523 may route data packets between the EPC 520 and external networkssuch as a network including the application server 130 (alternativelyreferred to as an “AF”) via an IP interface 125 (see e.g., FIG. 1). Inembodiments, the P-GW 523 may be communicatively coupled to anapplication server (application server 130 of FIG. 1 or PDN 530 in FIG.5) via an IP communications interface 125 (see, e.g., FIG. 1). The S5reference point between the P-GW 523 and the S-GW 522 may provide userplane tunneling and tunnel management between the P-GW 523 and the S-GW522. The S5 reference point may also be used for S-GW 522 relocation dueto UE 501 mobility and if the S-GW 522 needs to connect to anon-collocated P-GW 523 for the required PDN connectivity. The P-GW 523may further include a node for policy enforcement and charging datacollection (e.g., PCEF (not shown)). Additionally, the SGi referencepoint between the P-GW 523 and the packet data network (PDN) 530 may bean operator external public, a private PDN, or an intra operator packetdata network, for example, for provision of IMS services. The P-GW 523may be coupled with a PCRF 526 via a Gx reference point.

PCRF 526 is the policy and charging control element of the EPC 520. In anon-roaming scenario, there may be a single PCRF 526 in the Home PublicLand Mobile Network (HPLMN) associated with a UE 501's Internet ProtocolConnectivity Access Network (IP-CAN) session. In a roaming scenario withlocal breakout of traffic, there may be two PCRFs associated with a UE501's IP-CAN session, a Home PCRF (H-PCRF) within an HPLMN and a VisitedPCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). ThePCRF 526 may be communicatively coupled to the application server 530via the P-GW 523. The application server 530 may signal the PCRF 526 toindicate a new service flow and select the appropriate QoS and chargingparameters. The PCRF 526 may provision this rule into a PCEF (not shown)with the appropriate TFT and QCI, which commences the QoS and chargingas specified by the application server 530. The Gx reference pointbetween the PCRF 526 and the P-GW 523 may allow for the transfer of QoSpolicy and charging rules from the PCRF 526 to PCEF in the P-GW 523. AnRx reference point may reside between the PDN 530 (or “AF 530”) and thePCRF 526.

FIG. 6 illustrates an architecture of a system 600 including a second CN620 in accordance with various embodiments. The system 600 is shown toinclude a UE 601, which may be the same or similar to the UEs 101 and UE501 discussed previously; a (R)AN 610, which may be the same or similarto the RAN 110 and RAN 510 discussed previously, and which may includeRAN nodes 111 discussed previously; and a DN 603, which may be, forexample, operator services, Internet access or 3rd party services; and a5GC 620. The 5GC 620 may include an AUSF 622; an AMF 621; a SMF 624; aNEF 623; a PCF 626; a NRF 625; a UDM 627; an AF 628; a UPF 602; and aNSSF 629.

The UPF 602 may act as an anchor point for intra-RAT and inter-RATmobility, an external PDU session point of interconnect to DN 603, and abranching point to support multi-homed PDU session. The UPF 602 may alsoperform packet routing and forwarding, perform packet inspection,enforce the user plane part of policy rules, lawfully intercept packets(UP collection), perform traffic usage reporting, perform QoS handlingfor a user plane (e.g., packet filtering, gating, UL/DL rateenforcement), perform Uplink Traffic verification (e.g., SDF to QoS flowmapping), transport level packet marking in the uplink and downlink, andperform downlink packet buffering and downlink data notificationtriggering. UPF 602 may include an uplink classifier to support routingtraffic flows to a data network. The DN 603 may represent variousnetwork operator services, Internet access, or third party services. DN603 may include, or be similar to, application server 130 discussedpreviously. The UPF 602 may interact with the SMF 624 via an N4reference point between the SMF 624 and the UPF 602.

The AUSF 622 may store data for authentication of UE 601 and handleauthentication-related functionality. The AUSF 622 may facilitate acommon authentication framework for various access types. The AUSF 622may communicate with the AMF 621 via an N12 reference point between theAMF 621 and the AUSF 622; and may communicate with the UDM 627 via anN13 reference point between the UDM 627 and the AUSF 622. Additionally,the AUSF 622 may exhibit an Nausf service-based interface.

The AMF 621 may be responsible for registration management (e.g., forregistering UE 601, etc.), connection management, reachabilitymanagement, mobility management, and lawful interception of AMF-relatedevents, and access authentication and authorization. The AMF 621 may bea termination point for the an N11 reference point between the AMF 621and the SMF 624. The AMF 621 may provide transport for SM messagesbetween the UE 601 and the SMF 624, and act as a transparent proxy forrouting SM messages. AMF 621 may also provide transport for SMS messagesbetween UE 601 and an SMSF (not shown by FIG. 6). AMF 621 may act asSEAF, which may include interaction with the AUSF 622 and the UE 601,receipt of an intermediate key that was established as a result of theUE 601 authentication process. Where USIM based authentication is used,the AMF 621 may retrieve the security material from the AUSF 622. AMF621 may also include a SCM function, which receives a key from the SEAthat it uses to derive access-network specific keys. Furthermore, AMF621 may be a termination point of a RAN CP interface, which may includeor be an N2 reference point between the (R)AN 610 and the AMF 621; andthe AMF 621 may be a termination point of NAS (N1) signalling, andperform NAS ciphering and integrity protection.

AMF 621 may also support NAS signalling with a UE 601 over an N3 IWFinterface. The N3IWF may be used to provide access to untrustedentities. N3IWF may be a termination point for the N2 interface betweenthe (R)AN 610 and the AMF 621 for the control plane, and may be atermination point for the N3 reference point between the (R)AN 610 andthe UPF 602 for the user plane. As such, the AMF 621 may handle N2signalling from the SMF 624 and the AMF 621 for PDU sessions and QoS,encapsulate/de-encapsulate packets for IPSec and N3 tunnelling, mark N3user-plane packets in the uplink, and enforce QoS corresponding to N3packet marking taking into account QoS requirements associated with suchmarking received over N2. N3IWF may also relay uplink and downlinkcontrol-plane NAS signalling between the UE 601 and AMF 621 via an N1reference point between the UE 601 and the AMF 621, and relay uplink anddownlink user-plane packets between the UE 601 and UPF 602. The N3IWFalso provides mechanisms for IPsec tunnel establishment with the UE 601.The AMF 621 may exhibit an Namf service-based interface, and may be atermination point for an N14 reference point between two AMFs 621 and anN17 reference point between the AMF 621 and a 5G-EIR (not shown by FIG.6).

The UE 601 may need to register with the AMF 621 in order to receivenetwork services. RM is used to register or deregister the UE 601 withthe network (e.g., AMF 621), and establish a UE context in the network(e.g., AMF 621). The UE 601 may operate in an RM-REGISTERED state or anRM-DEREGISTERED state. In the RM-DEREGISTERED state, the UE 601 is notregistered with the network, and the UE context in AMF 621 holds novalid location or routing information for the UE 601 so the UE 601 isnot reachable by the AMF 621. In the RM-REGISTERED state, the UE 601 isregistered with the network, and the UE context in AMF 621 may hold avalid location or routing information for the UE 601 so the UE 601 isreachable by the AMF 621. In the RM-REGISTERED state, the UE 601 mayperform mobility Registration Update procedures, perform periodicRegistration Update procedures triggered by expiration of the periodicupdate timer (e.g., to notify the network that the UE 601 is stillactive), and perform a Registration Update procedure to update UEcapability information or to re-negotiate protocol parameters with thenetwork, among others.

The AMF 621 may store one or more RM contexts for the UE 601, where eachRM context is associated with a specific access to the network. The RMcontext may be a data structure, database object, etc. that indicates orstores, inter alia, a registration state per access type and theperiodic update timer. The AMF 621 may also store a 5GC MM context thatmay be the same or similar to the (E)MM context discussed previously. Invarious embodiments, the AMF 621 may store a CE mode B Restrictionparameter of the UE 601 in an associated MM context or RM context. TheAMF 621 may also derive the value, when needed, from the UE's usagesetting parameter already stored in the UE context (and/or MM/RMcontext).

CM may be used to establish and release a signaling connection betweenthe UE 601 and the AMF 621 over the N1 interface. The signalingconnection is used to enable NAS signaling exchange between the UE 601and the CN 620, and comprises both the signaling connection between theUE and the AN (e.g., RRC connection or UE-N3IWF connection for non-3GPPaccess) and the N2 connection for the UE 601 between the AN (e.g., RAN610) and the AMF 621. The UE 601 may operate in one of two CM states,CM-IDLE mode or CM-CONNECTED mode. When the UE 601 is operating in theCM-IDLE state/mode, the UE 601 may have no NAS signaling connectionestablished with the AMF 621 over the N1 interface, and there may be(R)AN 610 signaling connection (e.g., N2 and/or N3 connections) for theUE 601. When the UE 601 is operating in the CM-CONNECTED state/mode, theUE 601 may have an established NAS signaling connection with the AMF 621over the N1 interface, and there may be a (R)AN 610 signaling connection(e.g., N2 and/or N3 connections) for the UE 601. Establishment of an N2connection between the (R)AN 610 and the AMF 621 may cause the UE 601 totransition from CM-IDLE mode to CM-CONNECTED mode, and the UE 601 maytransition from the CM-CONNECTED mode to the CM-IDLE mode when N2signaling between the (R)AN 610 and the AMF 621 is released.

The SMF 624 may be responsible for SM (e.g., session establishment,modify and release, including tunnel maintain between UPF and AN node);UE IP address allocation and management (including optionalauthorization); selection and control of UP function; configuringtraffic steering at UPF to route traffic to proper destination;termination of interfaces toward policy control functions; controllingpart of policy enforcement and QoS; lawful intercept (for SM events andinterface to LI system); termination of SM parts of NAS messages;downlink data notification; initiating AN specific SM information, sentvia AMF over N2 to AN; and determining SSC mode of a session. SM refersto management of a PDU session, and a PDU session or “session” refers toa PDU connectivity service that provides or enables the exchange of PDUsbetween a UE 601 and a data network (DN) 603 identified by a DataNetwork Name (DNN). PDU sessions may be established upon UE 601 request,modified upon UE 601 and 5GC 620 request, and released upon UE 601 and5GC 620 request using NAS SM signaling exchanged over the N1 referencepoint between the UE 601 and the SMF 624. Upon request from anapplication server, the 5GC 620 may trigger a specific application inthe UE 601. In response to receipt of the trigger message, the UE 601may pass the trigger message (or relevant parts/information of thetrigger message) to one or more identified applications in the UE 601.The identified application(s) in the UE 601 may establish a PDU sessionto a specific DNN. The SMF 624 may check whether the UE 601 requests arecompliant with user subscription information associated with the UE 601.In this regard, the SMF 624 may retrieve and/or request to receiveupdate notifications on SMF 624 level subscription data from the UDM627.

The SMF 624 may include the following roaming functionality: handlinglocal enforcement to apply QoS SLAB (VPLMN); charging data collectionand charging interface (VPLMN); lawful intercept (in VPLMN for SM eventsand interface to LI system); and support for interaction with externalDN for transport of signalling for PDU sessionauthorization/authentication by external DN. An N16 reference pointbetween two SMFs 624 may be included in the system 600, which may bebetween another SMF 624 in a visited network and the SMF 624 in the homenetwork in roaming scenarios. Additionally, the SMF 624 may exhibit theNsmf service-based interface.

The NEF 623 may provide means for securely exposing the services andcapabilities provided by 3GPP network functions for third party,internal exposure/re-exposure, Application Functions (e.g., AF 628),edge computing or fog computing systems, etc. In such embodiments, theNEF 623 may authenticate, authorize, and/or throttle the AFs. NEF 623may also translate information exchanged with the AF 628 and informationexchanged with internal network functions. For example, the NEF 623 maytranslate between an AF-Service-Identifier and an internal 5GCinformation. NEF 623 may also receive information from other networkfunctions (NFs) based on exposed capabilities of other networkfunctions. This information may be stored at the NEF 623 as structureddata, or at a data storage NF using standardized interfaces. The storedinformation can then be re-exposed by the NEF 623 to other NFs and AFs,and/or used for other purposes such as analytics. Additionally, the NEF623 may exhibit an Nnef service-based interface.

The NRF 625 may support service discovery functions, receive NFdiscovery requests from NF instances, and provide the information of thediscovered NF instances to the NF instances. NRF 625 also maintainsinformation of available NF instances and their supported services. Asused herein, the terms “instantiate,” “instantiation,” and the likerefers to the creation of an instance, and an “instance” refers to aconcrete occurrence of an object, which may occur, for example, duringexecution of program code. Additionally, the NRF 625 may exhibit theNnrf service-based interface.

The PCF 626 may provide policy rules to control plane function(s) toenforce them, and may also support unified policy framework to governnetwork behaviour. The PCF 626 may also implement an FE to accesssubscription information relevant for policy decisions in a UDR of theUDM 627. The PCF 626 may communicate with the AMF 621 via an N15reference point between the PCF 626 and the AMF 621, which may include aPCF 626 in a visited network and the AMF 621 in case of roamingscenarios. The PCF 626 may communicate with the AF 628 via an N5reference point between the PCF 626 and the AF 628; and with the SMF 624via an N7 reference point between the PCF 626 and the SMF 624. Thesystem 600 and/or CN 620 may also include an N24 reference point betweenthe PCF 626 (in the home network) and a PCF 626 in a visited network.Additionally, the PCF 626 may exhibit an Npcf service-based interface.

The UDM 627 may handle subscription-related information to support thenetwork entities' handling of communication sessions, and may storesubscription data of UE 601. For example, subscription data may becommunicated between the UDM 627 and the AMF 621 via an N8 referencepoint between the UDM 627 and the AMF. The UDM 627 may include twoparts, an application FE and a UDR (the FE and UDR are not shown by FIG.6). The UDR may store subscription data and policy data for the UDM 627and the PCF 626, and/or structured data for exposure and applicationdata (including PFDs for application detection, application requestinformation for multiple UEs 601) for the NEF 623. The Nudrservice-based interface may be exhibited by the UDR 521 to allow the UDM627, PCF 626, and NEF 623 to access a particular set of the stored data,as well as to read, update (e.g., add, modify), delete, and subscribe tonotification of relevant data changes in the UDR. The UDM may include aUDM-FE, which is in charge of processing credentials, locationmanagement, subscription management and so on. Several different frontends may serve the same user in different transactions. The UDM-FEaccesses subscription information stored in the UDR and performsauthentication credential processing, user identification handling,access authorization, registration/mobility management, and subscriptionmanagement. The UDR may interact with the SMF 624 via an N10 referencepoint between the UDM 627 and the SMF 624. UDM 627 may also support SMSmanagement, wherein an SMS-FE implements the similar application logicas discussed previously. Additionally, the UDM 627 may exhibit the Nudmservice-based interface.

The AF 628 may provide application influence on traffic routing, provideaccess to the NCE, and interact with the policy framework for policycontrol. The NCE may be a mechanism that allows the 5GC 620 and AF 628to provide information to each other via NEF 623, which may be used foredge computing implementations. In such implementations, the networkoperator and third party services may be hosted close to the UE 601access point of attachment to achieve an efficient service deliverythrough the reduced end-to-end latency and load on the transportnetwork. For edge computing implementations, the 5GC may select a UPF602 close to the UE 601 and execute traffic steering from the UPF 602 toDN 603 via the N6 interface. This may be based on the UE subscriptiondata, UE location, and information provided by the AF 628. In this way,the AF 628 may influence UPF (re)selection and traffic routing. Based onoperator deployment, when AF 628 is considered to be a trusted entity,the network operator may permit AF 628 to interact directly withrelevant NFs. Additionally, the AF 628 may exhibit an Naf service-basedinterface.

The NSSF 629 may select a set of network slice instances serving the UE601. The NSSF 629 may also determine allowed NSSAI and the mapping tothe subscribed S-NSSAIs, if needed. The NSSF 629 may also determine theAMF set to be used to serve the UE 601, or a list of candidate AMF(s)621 based on a suitable configuration and possibly by querying the NRF625. The selection of a set of network slice instances for the UE 601may be triggered by the AMF 621 with which the UE 601 is registered byinteracting with the NSSF 629, which may lead to a change of AMF 621.The NSSF 629 may interact with the AMF 621 via an N22 reference pointbetween AMF 621 and NSSF 629; and may communicate with another NSSF 629in a visited network via an N31 reference point (not shown by FIG. 6).Additionally, the NSSF 629 may exhibit an Nnssf service-based interface.

As discussed previously, the CN 620 may include an SMSF, which may beresponsible for SMS subscription checking and verification, and relayingSM messages to/from the UE 601 to/from other entities, such as anSMS-GMSC/IWMSC/SMS-router. The SMS may also interact with AMF 621 andUDM 627 for a notification procedure that the UE 601 is available forSMS transfer (e.g., set a UE not reachable flag, and notifying UDM 627when UE 601 is available for SMS).

The CN 120 may also include other elements that are not shown by FIG. 6,such as a Data Storage system/architecture, a 5G-EIR, a SEPP, and thelike. The Data Storage system may include a SDSF, an UDSF, and/or thelike. Any NF may store and retrieve unstructured data into/from the UDSF(e.g., UE contexts), via N18 reference point between any NF and the UDSF(not shown by FIG. 6). Individual NFs may share a UDSF for storing theirrespective unstructured data or individual NFs may each have their ownUDSF located at or near the individual NFs. Additionally, the UDSF mayexhibit an Nudsf service-based interface (not shown by FIG. 6). The5G-EIR may be an NF that checks the status of PEI for determiningwhether particular equipment/entities are blacklisted from the network;and the SEPP may be a non-transparent proxy that performs topologyhiding, message filtering, and policing on inter-PLMN control planeinterfaces.

Additionally, there may be many more reference points and/orservice-based interfaces between the NF services in the NFs; however,these interfaces and reference points have been omitted from FIG. 6 forclarity. In one example, the CN 620 may include an Nx interface, whichis an inter-CN interface between the MME (e.g., MME 521) and the AMF 621in order to enable interworking between CN 620 and CN 520. Other exampleinterfaces/reference points may include an N5g-EIR service-basedinterface exhibited by a 5G-EIR, an N27 reference point between the NRFin the visited network and the NRF in the home network; and an N31reference point between the NSSF in the visited network and the NSSF inthe home network.

FIG. 7 illustrates an example of infrastructure equipment 700 inaccordance with various embodiments. The infrastructure equipment 700(or “system 700”) may be implemented as a base station, radio head, RANnode such as the RAN nodes 111 and/or AP 106 shown and describedpreviously, application server(s) 130, and/or any other element/devicediscussed herein. In other examples, the system 700 could be implementedin or by a UE.

The system 700 includes application circuitry 705, baseband circuitry710, one or more radio front end modules (RFEMs) 715, memory circuitry720, power management integrated circuitry (PMIC) 725, power teecircuitry 730, network controller circuitry 735, network interfaceconnector 740, satellite positioning circuitry 745, and user interface750. In some embodiments, the device 700 may include additional elementssuch as, for example, memory/storage, display, camera, sensor, orinput/output (I/O) interface. In other embodiments, the componentsdescribed below may be included in more than one device. For example,said circuitries may be separately included in more than one device forCRAN, vBBU, or other like implementations.

Application circuitry 705 includes circuitry such as, but not limited toone or more processors (or processor cores), cache memory, and one ormore of low drop-out voltage regulators (LDOs), interrupt controllers,serial interfaces such as SPI, I²C or universal programmable serialinterface module, real time clock (RTC), timer-counters includinginterval and watchdog timers, general purpose input/output (I/O or IO),memory card controllers such as Secure Digital (SD) MultiMediaCard (MMC)or similar, Universal Serial Bus (USB) interfaces, Mobile IndustryProcessor Interface (MIPI) interfaces and Joint Test Access Group (JTAG)test access ports. The processors (or cores) of the applicationcircuitry 705 may be coupled with or may include memory/storage elementsand may be configured to execute instructions stored in thememory/storage to enable various applications or operating systems torun on the system 700. In some implementations, the memory/storageelements may be on-chip memory circuitry, which may include any suitablevolatile and/or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM,Flash memory, solid-state memory, and/or any other type of memory devicetechnology, such as those discussed herein.

The processor(s) of application circuitry 705 may include, for example,one or more processor cores (CPUs), one or more application processors,one or more graphics processing units (GPUs), one or more reducedinstruction set computing (RISC) processors, one or more Acorn RISCMachine (ARM) processors, one or more complex instruction set computing(CISC) processors, one or more digital signal processors (DSP), one ormore FPGAs, one or more PLDs, one or more ASICs, one or moremicroprocessors or controllers, or any suitable combination thereof. Insome embodiments, the application circuitry 705 may comprise, or may be,a special-purpose processor/controller to operate according to thevarious embodiments herein. As examples, the processor(s) of applicationcircuitry 705 may include one or more Intel Pentium®, Core®, or Xeon®processor(s); Advanced Micro Devices (AMD) Ryzen® processor(s),Accelerated Processing Units (APUs), or Epyc® processors; ARM-basedprocessor(s) licensed from ARM Holdings, Ltd. such as the ARM Cortex-Afamily of processors and the ThunderX2® provided by Cavium™, Inc.; aMIPS-based design from MIPS Technologies, Inc. such as MIPS WarriorP-class processors; and/or the like. In some embodiments, the system 700may not utilize application circuitry 705, and instead may include aspecial-purpose processor/controller to process IP data received from anEPC or 5GC, for example.

In some implementations, the application circuitry 705 may include oneor more hardware accelerators, which may be microprocessors,programmable processing devices, or the like. The one or more hardwareaccelerators may include, for example, computer vision (CV) and/or deeplearning (DL) accelerators. As examples, the programmable processingdevices may be one or more a field-programmable devices (FPDs) such asfield-programmable gate arrays (FPGAs) and the like; programmable logicdevices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs(HCPLDs), and the like; ASICs such as structured ASICs and the like;programmable SoCs (PSoCs); and the like. In such implementations, thecircuitry of application circuitry 705 may comprise logic blocks orlogic fabric, and other interconnected resources that may be programmedto perform various functions, such as the procedures, methods,functions, etc. of the various embodiments discussed herein. In suchembodiments, the circuitry of application circuitry 705 may includememory cells (e.g., erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), flashmemory, static memory (e.g., static random access memory (SRAM),anti-fuses, etc.)) used to store logic blocks, logic fabric, data, etc.in look-up-tables (LUTs) and the like.

The baseband circuitry 710 may be implemented, for example, as asolder-down substrate including one or more integrated circuits, asingle packaged integrated circuit soldered to a main circuit board or amulti-chip module containing two or more integrated circuits. Thevarious hardware electronic elements of baseband circuitry 710 arediscussed infra with regard to FIG. 10.

User interface circuitry 750 may include one or more user interfacesdesigned to enable user interaction with the system 700 or peripheralcomponent interfaces designed to enable peripheral component interactionwith the system 700. User interfaces may include, but are not limitedto, one or more physical or virtual buttons (e.g., a reset button), oneor more indicators (e.g., light emitting diodes (LEDs)), a physicalkeyboard or keypad, a mouse, a touchpad, a touchscreen, speakers orother audio emitting devices, microphones, a printer, a scanner, aheadset, a display screen or display device, etc. Peripheral componentinterfaces may include, but are not limited to, a nonvolatile memoryport, a universal serial bus (USB) port, an audio jack, a power supplyinterface, etc.

The radio front end modules (RFEMs) 715 may comprise a millimeter wave(mmWave) RFEM and one or more sub-mmWave radio frequency integratedcircuits (RFICs). In some implementations, the one or more sub-mmWaveRFICs may be physically separated from the mmWave RFEM. The RFICs mayinclude connections to one or more antennas or antenna arrays (see e.g.,antenna array 1011 of FIG. 10 infra), and the RFEM may be connected tomultiple antennas. In alternative implementations, both mmWave andsub-mmWave radio functions may be implemented in the same physical RFEM715, which incorporates both mmWave antennas and sub-mmWave.

The memory circuitry 720 may include one or more of volatile memoryincluding dynamic random access memory (DRAM) and/or synchronous dynamicrandom access memory (SDRAM), and nonvolatile memory (NVM) includinghigh-speed electrically erasable memory (commonly referred to as Flashmemory), phase change random access memory (PRAM), magnetoresistiverandom access memory (MRAM), etc., and may incorporate thethree-dimensional (3D) cross-point (XPOINT) memories from Intel® andMicron®. Memory circuitry 720 may be implemented as one or more ofsolder down packaged integrated circuits, socketed memory modules andplug-in memory cards.

The PMIC 725 may include voltage regulators, surge protectors, poweralarm detection circuitry, and one or more backup power sources such asa battery or capacitor. The power alarm detection circuitry may detectone or more of brown out (under-voltage) and surge (over-voltage)conditions. The power tee circuitry 730 may provide for electrical powerdrawn from a network cable to provide both power supply and dataconnectivity to the infrastructure equipment 700 using a single cable.

The network controller circuitry 735 may provide connectivity to anetwork using a standard network interface protocol such as Ethernet,Ethernet over GRE Tunnels, Ethernet over Multiprotocol Label Switching(MPLS), or some other suitable protocol. Network connectivity may beprovided to/from the infrastructure equipment 700 via network interfaceconnector 740 using a physical connection, which may be electrical(commonly referred to as a “copper interconnect”), optical, or wireless.The network controller circuitry 735 may include one or more dedicatedprocessors and/or FPGAs to communicate using one or more of theaforementioned protocols. In some implementations, the networkcontroller circuitry 735 may include multiple controllers to provideconnectivity to other networks using the same or different protocols.

The positioning circuitry 745 includes circuitry to receive and decodesignals transmitted/broadcasted by a positioning network of a globalnavigation satellite system (GNSS). Examples of navigation satelliteconstellations (or GNSS) include United States' Global PositioningSystem (GPS), Russia's Global Navigation System (GLONASS), the EuropeanUnion's Galileo system, China's BeiDou Navigation Satellite System, aregional navigation system or GNSS augmentation system (e.g., Navigationwith Indian Constellation (NAVIC), Japan's Quasi-Zenith Satellite System(QZSS), France's Doppler Orbitography and Radio-positioning Integratedby Satellite (DORIS), etc.), or the like. The positioning circuitry 745comprises various hardware elements (e.g., including hardware devicessuch as switches, filters, amplifiers, antenna elements, and the like tofacilitate OTA communications) to communicate with components of apositioning network, such as navigation satellite constellation nodes.In some embodiments, the positioning circuitry 745 may include aMicro-Technology for Positioning, Navigation, and Timing (Micro-PNT) ICthat uses a master timing clock to perform position tracking/estimationwithout GNSS assistance. The positioning circuitry 745 may also be partof, or interact with, the baseband circuitry 710 and/or RFEMs 715 tocommunicate with the nodes and components of the positioning network.The positioning circuitry 745 may also provide position data and/or timedata to the application circuitry 705, which may use the data tosynchronize operations with various infrastructure (e.g., RAN nodes 111,etc.), or the like.

The components shown by FIG. 7 communicate with one another usinginterface circuitry, which may include interconnect (IX) 706. The IX 706may include any number of bus and/or IX technologies such as industrystandard architecture (ISA), extended ISA (EISA), inter-integratedcircuit (I²C), an serial peripheral interface (SPI), point-to-pointinterfaces, power management bus (PMBus), peripheral componentinterconnect (PCI), PCI express (PCIe), Intel® Ultra Path Interface(UPI), Intel® Accelerator Link (IAL), Common Application ProgrammingInterface (CAPI), Intel® QuickPath interconnect (QPI), Ultra PathInterconnect (UPI), Intel® Omni-Path Architecture (OPA) IX, RapidIO™system IXs, Cache Coherent Interconnect for Accelerators (CCIA), Gen-ZConsortium IXs, Open Coherent Accelerator Processor Interface (OpenCAPI)IX, a HyperTransport interconnect, and/or any number of other IXtechnologies. The IX technology may be a proprietary bus, for example,used in an SoC based system.

FIG. 8 illustrates an example of a platform 800 (or “device 800”) inaccordance with various embodiments. In embodiments, the computerplatform 800 may be suitable for use as UEs 101, 501, 601, applicationservers 130, and/or any other element/device discussed herein. Theplatform 800 may include any combinations of the components shown in theexample. The components of platform 800 may be implemented as integratedcircuits (ICs), portions thereof, discrete electronic devices, or othermodules, logic, hardware, software, firmware, or a combination thereofadapted in the computer platform 800, or as components otherwiseincorporated within a chassis of a larger system. The block diagram ofFIG. 8 is intended to show a high level view of components of thecomputer platform 800. However, some of the components shown may beomitted, additional components may be present, and different arrangementof the components shown may occur in other implementations.

Application circuitry 805 includes circuitry such as, but not limited toone or more processors (or processor cores), cache memory, and one ormore of LDOs, interrupt controllers, serial interfaces such as SPI, I²Cor universal programmable serial interface module, RTC, timer-countersincluding interval and watchdog timers, general purpose I/O, memory cardcontrollers such as SD MMC or similar, USB interfaces, MIPI interfaces,and JTAG test access ports. The processors (or cores) of the applicationcircuitry 805 may be coupled with or may include memory/storage elementsand may be configured to execute instructions stored in thememory/storage to enable various applications or operating systems torun on the system 800. In some implementations, the memory/storageelements may be on-chip memory circuitry, which may include any suitablevolatile and/or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM,Flash memory, solid-state memory, and/or any other type of memory devicetechnology, such as those discussed herein.

The processor(s) of application circuitry 805 may include, for example,one or more processor cores, one or more application processors, one ormore GPUs, one or more RISC processors, one or more ARM processors, oneor more CISC processors, one or more DSP, one or more FPGAs, one or morePLDs, one or more ASICs, one or more microprocessors or controllers, amultithreaded processor, an ultra-low voltage processor, an embeddedprocessor, some other known processing element, or any suitablecombination thereof. The processors (or cores) of the applicationcircuitry 805 may be coupled with or may include memory/storage and maybe configured to execute instructions stored in the memory/storage toenable various applications or operating systems to run on the system800. In these embodiments, the processors (or cores) of the applicationcircuitry 805 are configured to operate application software to providea specific service to a user of the system 800. In some embodiments, theapplication circuitry 805 may comprise, or may be, a special-purposeprocessor/controller to operate according to the various embodimentsherein.

As examples, the processor(s) of application circuitry 805 may includean Intel® Architecture Core™ based processor, such as a Quark™, anAtom™, an i3, an i5, an i7, or an MCU-class processor, or another suchprocessor available from Intel® Corporation, Santa Clara, Calif. Theprocessors of the application circuitry 805 may also be one or more ofAdvanced Micro Devices (AMD) Ryzen® processor(s) or AcceleratedProcessing Units (APUs); A5-A9 processor(s) from Apple® Inc.,Snapdragon™ processor(s) from Qualcomm® Technologies, Inc., TexasInstruments, Inc.® Open Multimedia Applications Platform (OMAP)™processor(s); a MIPS-based design from MIPS Technologies, Inc. such asMIPS Warrior M-class, Warrior I-class, and Warrior P-class processors;an ARM-based design licensed from ARM Holdings, Ltd., such as the ARMCortex-A, Cortex-R, and Cortex-M family of processors; or the like. Insome implementations, the application circuitry 805 may be a part of asystem on a chip (SoC) in which the application circuitry 805 and othercomponents are formed into a single integrated circuit, or a singlepackage, such as the Edison™ or Galileo™ SoC boards from Intel®Corporation. Other examples of the processor circuitry of applicationcircuitry 705 are mentioned elsewhere in the present disclosure.

Additionally or alternatively, application circuitry 805 may includecircuitry such as, but not limited to, one or more a field-programmabledevices (FPDs) such as FPGAs and the like; programmable logic devices(PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), andthe like; ASICs such as structured ASICs and the like; programmable SoCs(PSoCs); and the like. In such embodiments, the circuitry of applicationcircuitry 805 may comprise logic blocks or logic fabric, and otherinterconnected resources that may be programmed to perform variousfunctions, such as the procedures, methods, functions, etc. of thevarious embodiments discussed herein. In such embodiments, the circuitryof application circuitry 805 may include memory cells (e.g., erasableprogrammable read-only memory (EPROM), electrically erasableprogrammable read-only memory (EEPROM), flash memory, static memory(e.g., static random access memory (SRAM), anti-fuses, etc.)) used tostore logic blocks, logic fabric, data, etc. in look-up tables (LUTs)and the like.

The baseband circuitry 810 may be implemented, for example, as asolder-down substrate including one or more integrated circuits, asingle packaged integrated circuit soldered to a main circuit board or amulti-chip module containing two or more integrated circuits. Thebaseband circuitry 810 may include circuitry such as, but not limitedto, one or more single-core or multi-core processors (e.g., one or morebaseband processors) or control logic to process baseband signalsreceived from a receive signal path of the RFEMs 815, and to generatebaseband signals to be provided to the RFEMs 815 via a transmit signalpath. In various embodiments, the baseband circuitry 810 may implement areal-time OS (RTOS) to manage resources of the baseband circuitry 810,schedule tasks, etc. Examples of the RTOS may include Operating SystemEmbedded (OSE)™ provided by Enea®, Nucleus RTOS™ provided by MentorGraphics®, Versatile Real-Time Executive (VRTX) provided by MentorGraphics®, ThreadX™ provided by Express Logic®, FreeRTOS, REX OSprovided by Qualcomm®, OKL4 provided by Open Kernel (OK) Labs®, or anyother suitable RTOS, such as those discussed herein. The varioushardware electronic elements of baseband circuitry 810 are discussedinfra with regard to FIG. 10.

The RFEMs 815 may comprise a millimeter wave (mmWave) RFEM and one ormore sub-mmWave radio frequency integrated circuits (RFICs). In someimplementations, the one or more sub-mmWave RFICs may be physicallyseparated from the mmWave RFEM. The RFICs may include connections to oneor more antennas or antenna arrays (see e.g., antenna array 1011 of FIG.10 infra), and the RFEM may be connected to multiple antennas. Inalternative implementations, both mmWave and sub-mmWave radio functionsmay be implemented in the same physical RFEM 815, which incorporatesboth mmWave antennas and sub-mmWave.

The memory circuitry 820 may include any number and type of memorydevices used to provide for a given amount of system memory. Asexamples, the memory circuitry 820 may include one or more of volatilememory including random access memory (RAM), dynamic RAM (DRAM) and/orsynchronous dynamic RAM (SDRAM), and nonvolatile memory (NVM) includinghigh-speed electrically erasable memory (commonly referred to as Flashmemory), phase change random access memory (PRAM), magnetoresistiverandom access memory (MRAM), etc. The memory circuitry 820 may bedeveloped in accordance with a Joint Electron Devices EngineeringCouncil (JEDEC) low power double data rate (LPDDR)-based design, such asLPDDR2, LPDDR3, LPDDR4, or the like. Memory circuitry 820 may beimplemented as one or more of solder down packaged integrated circuits,single die package (SDP), dual die package (DDP) or quad die package(Q17P), socketed memory modules, dual inline memory modules (DIMMs)including microDIMMs or MiniDIMMs, and/or soldered onto a motherboardvia a ball grid array (BGA). In low power implementations, the memorycircuitry 820 may be on-die memory or registers associated with theapplication circuitry 805. To provide for persistent storage ofinformation such as data, applications, operating systems and so forth,memory circuitry 820 may include one or more mass storage devices, whichmay include, inter alia, a solid state disk drive (SSDD), hard diskdrive (HDD), a micro HDD, resistance change memories, phase changememories, holographic memories, or chemical memories, among others. Forexample, the computer platform 800 may incorporate the three-dimensional(3D) cross-point (XPOINT) memories from Intel® and Micron®.

Removable memory circuitry 823 may include devices, circuitry,enclosures/housings, ports or receptacles, etc. used to couple portabledata storage devices with the platform 800. These portable data storagedevices may be used for mass storage purposes, and may include, forexample, flash memory cards (e.g., Secure Digital (SD) cards, microSDcards, xD picture cards, and the like), and USB flash drives, opticaldiscs, external HDDs, and the like.

In some implementations, the memory circuitry 820 and/or the removablememory 823 provide persistent storage of information such as data,applications, operating systems (OS), and so forth. The persistentstorage circuitry is configured to store computational logic (or“modules”) in the form of software, firmware, or hardware commands toimplement the techniques described herein. The computational logic maybe employed to store working copies and/or permanent copies of computerprograms (or data to create the computer programs) for the operation ofvarious components of platform 800 (e.g., drivers, etc.), an operatingsystem of platform 800, one or more applications, and/or for carryingout the embodiments discussed herein. The computational logic may bestored or loaded into memory circuitry 820 as instructions (or data tocreate the instructions) for execution by the application circuitry 805to provide the functions described herein. The various elements may beimplemented by assembler instructions supported by processor circuitryor high-level languages that may be compiled into such instructions (ordata to create the instructions). The permanent copy of the programminginstructions may be placed into persistent storage devices of persistentstorage circuitry in the factory or in the field through, for example, adistribution medium (not shown), through a communication interface(e.g., from a distribution server (not shown)), or OTA.

In an example, the instructions provided via the memory circuitry 820and/or the persistent storage circuitry are embodied as one or morenon-transitory computer readable storage media including program code, acomputer program product (or data to create the computer program) withthe computer program or data, to direct the application circuitry 805 ofplatform 800 to perform electronic operations in the platform 800,and/or to perform a specific sequence or flow of actions, for example,as described with respect to the flowchart(s) and block diagram(s) ofoperations and functionality depicted infra (see e.g., FIGS. 12-14). Theapplication circuitry 805 accesses the one or more non-transitorycomputer readable storage media over the IX 806.

Although the instructions and/or computational logic have been describedas code blocks included in the memory circuitry 820 and/or code blocksin the persistent storage circuitry, it should be understood that any ofthe code blocks may be replaced with hardwired circuits, for example,built into an FPGA, ASIC, or some other suitable circuitry. For example,where application circuitry 805 includes (e.g., FPGA based) hardwareaccelerators as well as processor cores, the hardware accelerators(e.g., the FPGA cells) may be pre-configured (e.g., with appropriate bitstreams) with the aforementioned computational logic to perform some orall of the functions discussed previously (in lieu of employment ofprogramming instructions to be executed by the processor core(s)).

The platform 800 may also include interface circuitry (not shown) thatis used to connect external devices with the platform 800. The externaldevices connected to the platform 800 via the interface circuitryinclude sensor circuitry 821 and actuators 822, as well as removablememory devices coupled to removable memory circuitry 823.

The sensor circuitry 821 include devices, modules, or subsystems whosepurpose is to detect events or changes in its environment and send theinformation (sensor data) about the detected events to some other adevice, module, subsystem, etc. Examples of such sensors include, interalia, inertia measurement units (IMUS) comprising accelerometers,gyroscopes, and/or magnetometers; microelectromechanical systems (MEMS)or nanoelectromechanical systems (NEMS) comprising 3-axisaccelerometers, 3-axis gyroscopes, and/or magnetometers; level sensors;flow sensors; temperature sensors (e.g., thermistors); pressure sensors;barometric pressure sensors; gravimeters; altimeters; image capturedevices (e.g., cameras or lensless apertures); light detection andranging (LiDAR) sensors; proximity sensors (e.g., infrared radiationdetector and the like), depth sensors, ambient light sensors, ultrasonictransceivers; microphones or other like audio capture devices; etc.

Actuators 822 include devices, modules, or subsystems whose purpose isto enable platform 800 to change its state, position, and/ororientation, or move or control a mechanism or (sub)system. Theactuators 822 comprise electrical and/or mechanical devices for movingor controlling a mechanism or system, and converts energy (e.g.,electric current or moving air and/or liquid) into some kind of motion.The actuators 822 may include one or more electronic (orelectrochemical) devices, such as piezoelectric biomorphs, solid stateactuators, solid state relays (SSRs), shape-memory alloy-basedactuators, electroactive polymer-based actuators, relay driverintegrated circuits (ICs), and/or the like. The actuators 822 mayinclude one or more electromechanical devices such as pneumaticactuators, hydraulic actuators, electromechanical switches includingelectromechanical relays (EMRs), motors (e.g., DC motors, steppermotors, servomechanisms, etc.), wheels, thrusters, propellers, claws,clamps, hooks, an audible sound generator, and/or other likeelectromechanical components. The platform 1000 may be configured tooperate one or more actuators 822 based on one or more captured eventsand/or instructions or control signals received from a service providerand/or various client systems.

In some implementations, the interface circuitry may connect theplatform 800 with positioning circuitry 845. The positioning circuitry845 includes circuitry to receive and decode signalstransmitted/broadcasted by a positioning network of a GNSS. Examples ofnavigation satellite constellations (or GNSS) include United States'GPS, Russia's GLONASS, the European Union's Galileo system, China'sBeiDou Navigation Satellite System, a regional navigation system or GNSSaugmentation system (e.g., NAVIC), Japan's QZSS, France's DORIS, etc.),or the like. The positioning circuitry 845 comprises various hardwareelements (e.g., including hardware devices such as switches, filters,amplifiers, antenna elements, and the like to facilitate OTAcommunications) to communicate with components of a positioning network,such as navigation satellite constellation nodes. In some embodiments,the positioning circuitry 845 may include a Micro-PNT IC that uses amaster timing clock to perform position tracking/estimation without GNSSassistance. The positioning circuitry 845 may also be part of, orinteract with, the baseband circuitry 810 and/or RFEMs 815 tocommunicate with the nodes and components of the positioning network.The positioning circuitry 845 may also provide position data and/or timedata to the application circuitry 805, which may use the data tosynchronize operations with various infrastructure (e.g., radio basestations), for turn-by-turn navigation applications, or the like

In some implementations, the interface circuitry may connect theplatform 800 with Near-Field Communication (NFC) circuitry 840. NFCcircuitry 840 is configured to provide contactless, short-rangecommunications based on radio frequency identification (RFID) standards,wherein magnetic field induction is used to enable communication betweenNFC circuitry 840 and NFC-enabled devices external to the platform 800(e.g., an “NFC touchpoint”). NFC circuitry 840 comprises an NFCcontroller coupled with an antenna element and a processor coupled withthe NFC controller. The NFC controller may be a chip/IC providing NFCfunctionalities to the NFC circuitry 840 by executing NFC controllerfirmware and an NFC stack. The NFC stack may be executed by theprocessor to control the NFC controller, and the NFC controller firmwaremay be executed by the NFC controller to control the antenna element toemit short-range RF signals. The RF signals may power a passive NFC tag(e.g., a microchip embedded in a sticker or wristband) to transmitstored data to the NFC circuitry 840, or initiate data transfer betweenthe NFC circuitry 840 and another active NFC device (e.g., a smartphoneor an NFC-enabled POS terminal) that is proximate to the platform 800.

The driver circuitry 846 may include software and hardware elements thatoperate to control particular devices that are embedded in the platform800, attached to the platform 800, or otherwise communicatively coupledwith the platform 800. The driver circuitry 846 may include individualdrivers allowing other components of the platform 800 to interact withor control various input/output (I/O) devices that may be presentwithin, or connected to, the platform 800. For example, driver circuitry846 may include a display driver to control and allow access to adisplay device, a touchscreen driver to control and allow access to atouchscreen interface of the platform 800, sensor drivers to obtainsensor readings of sensor circuitry 821 and control and allow access tosensor circuitry 821, actuator drivers to obtain actuator positions ofthe actuators 822 and/or control and allow access to the actuators 822,a camera driver to control and allow access to an embedded image capturedevice, audio drivers to control and allow access to one or more audiodevices.

The power management integrated circuitry (PMIC) 825 (also referred toas “power management circuitry 825”) may manage power provided tovarious components of the platform 800. In particular, with respect tothe baseband circuitry 810, the PMIC 825 may control power-sourceselection, voltage scaling, battery charging, or DC-to-DC conversion.The PMIC 825 may often be included when the platform 800 is capable ofbeing powered by a battery 830, for example, when the device is includedin a UE 101, 501, 601.

In some embodiments, the PMIC 825 may control, or otherwise be part of,various power saving mechanisms of the platform 800. For example, if theplatform 800 is in an RRC_Connected state, where it is still connectedto the RAN node as it expects to receive traffic shortly, then it mayenter a state known as DRX after a period of inactivity. During thisstate, the platform 800 may power down for brief intervals of time andthus save power. If there is no data traffic activity for an extendedperiod of time, then the platform 800 may transition off to an RRC_Idlestate, where it disconnects from the network and does not performoperations such as channel quality feedback, handover, etc. The platform800 goes into a very low power state and it performs paging where againit periodically wakes up to listen to the network and then powers downagain. The platform 800 may not receive data in this state; in order toreceive data, it must transition back to RRC_Connected state. Anadditional power saving mode may allow a device to be unavailable to thenetwork for periods longer than a paging interval (ranging from secondsto a few hours). During this time, the device is totally unreachable tothe network and may power down completely. Any data sent during thistime incurs a large delay and it is assumed the delay is acceptable.

A battery 830 may power the platform 800, although in some examples theplatform 800 may be mounted deployed in a fixed location, and may have apower supply coupled to an electrical grid. The battery 830 may be alithium ion battery, a metal-air battery, such as a zinc-air battery, analuminum-air battery, a lithium-air battery, and the like. In someimplementations, such as in V2X applications, the battery 830 may be atypical lead-acid automotive battery.

In some implementations, the battery 830 may be a “smart battery,” whichincludes or is coupled with a Battery Management System (BMS) or batterymonitoring integrated circuitry. The BMS may be included in the platform800 to track the state of charge (SoCh) of the battery 830. The BMS maybe used to monitor other parameters of the battery 830 to providefailure predictions, such as the state of health (SoH) and the state offunction (SoF) of the battery 830. The BMS may communicate theinformation of the battery 830 to the application circuitry 805 or othercomponents of the platform 800. The BMS may also include ananalog-to-digital (ADC) convertor that allows the application circuitry805 to directly monitor the voltage of the battery 830 or the currentflow from the battery 830. The battery parameters may be used todetermine actions that the platform 800 may perform, such astransmission frequency, network operation, sensing frequency, and thelike.

A power block, or other power supply coupled to an electrical grid maybe coupled with the BMS to charge the battery 830. In some examples, thepower block XS30 may be replaced with a wireless power receiver toobtain the power wirelessly, for example, through a loop antenna in thecomputer platform 800. In these examples, a wireless battery chargingcircuit may be included in the BMS. The specific charging circuitschosen may depend on the size of the battery 830, and thus, the currentrequired. The charging may be performed using the Airfuel standardpromulgated by the Airfuel Alliance, the Qi wireless charging standardpromulgated by the Wireless Power Consortium, or the Rezence chargingstandard promulgated by the Alliance for Wireless Power, among others.

User interface circuitry 850 includes various input/output (I/O) devicespresent within, or connected to, the platform 800, and includes one ormore user interfaces designed to enable user interaction with theplatform 800 and/or peripheral component interfaces designed to enableperipheral component interaction with the platform 800. The userinterface circuitry 850 includes input device circuitry and outputdevice circuitry. Input device circuitry includes any physical orvirtual means for accepting an input including, inter alia, one or morephysical or virtual buttons (e.g., a reset button), a physical keyboard,keypad, mouse, touchpad, touchscreen, microphones, scanner, headset,and/or the like. The output device circuitry includes any physical orvirtual means for showing information or otherwise conveyinginformation, such as sensor readings, actuator position(s), or otherlike information. Output device circuitry may include any number and/orcombinations of audio or visual display, including, inter alia, one ormore simple visual outputs/indicators (e.g., binary status indicators(e.g., light emitting diodes (LEDs)) and multi-character visual outputs,or more complex outputs such as display devices or touchscreens (e.g.,Liquid Chrystal Displays (LCD), LED displays, quantum dot displays,projectors, etc.), with the output of characters, graphics, multimediaobjects, and the like being generated or produced from the operation ofthe platform 800. The output device circuitry may also include speakersor other audio emitting devices, printer(s), and/or the like. In someembodiments, the sensor circuitry 821 may be used as the input devicecircuitry (e.g., an image capture device, motion capture device, or thelike) and one or more actuators 822 may be used as the output devicecircuitry (e.g., an actuator to provide haptic feedback or the like). Inanother example, NFC circuitry comprising an NFC controller coupled withan antenna element and a processing device may be included to readelectronic tags and/or connect with another NFC-enabled device.Peripheral component interfaces may include, but are not limited to, anon-volatile memory port, a USB port, an audio jack, a power supplyinterface, etc.

The components shown by FIG. 8 communicate with one another usinginterface circuitry, which may include interconnect (IX) 806. The IX 806may include any number of bus and/or IX technologies such as ISA, EISA,I²C, SPI, point-to-point interfaces, PMBus, PCI) PCIe, Intel® UPI, IAL,CAPI, Intel® QPI, UPI, Intel® OPA IX, RapidIO™ system IXs, CCIA, Gen-ZConsortium IXs, OpenCAPI IX, a HyperTransport interconnect, Time-TriggerProtocol (TTP) system, a FlexRay system, and/or any number of other IXtechnologies. The IX technology may be a proprietary bus, for example,used in an SoC based system.

FIG. 9 illustrates components, according to some example embodiments,able to read instructions from a machine-readable or computer-readablemedium (e.g., a non-transitory machine-readable storage medium) andperform any one or more of the methodologies discussed herein.Specifically, FIG. 9 shows a diagrammatic representation of hardwareresources 900 including one or more processors (or processor cores) 910,one or more memory/storage devices 920, and one or more communicationresources 930, each of which may be communicatively coupled via a bus940. For embodiments where node virtualization (e.g., NFV) is utilized,a hypervisor 902 may be executed to provide an execution environment forone or more network slices/sub-slices to utilize the hardware resources900.

The processors 910 may include, for example, a processor 912 and aprocessor 914. The processor(s) 910 may be, for example, a CPU, areduced instruction set computing (RISC) processor, a CISC processor, aGPU, a DSP such as a baseband processor, an ASIC, an FPGA, a RFIC,another processor (including those discussed herein), or any suitablecombination thereof. The memory/storage devices 920 may include mainmemory, disk storage, or any suitable combination thereof. Thememory/storage devices 920 may include, but are not limited to, any typeof volatile or nonvolatile memory such as DRAM, SRAM, EPROM, EEPROM,Flash memory, solid-state storage, etc.

The communication resources 930 may include interconnection or networkinterface components or other suitable devices to communicate with oneor more peripheral devices 904 or one or more databases 906 via anetwork 908. For example, the communication resources 930 may includewired communication components (e.g., for coupling via USB), cellularcommunication components, NFC components, Bluetooth® (or Bluetooth® LowEnergy) components, Wi-Fi® components, and other communicationcomponents, such as those discussed herein.

Instructions 950 may comprise software, a program, an application, anapplet, an app, or other executable code for causing at least any of theprocessors 910 to perform any one or more of the methodologies discussedherein. The instructions 950 may reside, completely or partially, withinat least one of the processors 910 (e.g., within the processor's cachememory), the memory/storage devices 920, or any suitable combinationthereof. Furthermore, any portion of the instructions 950 may betransferred to the hardware resources 900 from any combination of theperipheral devices 904 or the databases 906. Accordingly, the memory ofprocessors 910, the memory/storage devices 920, the peripheral devices904, and the databases 906 are examples of computer-readable andmachine-readable media.

FIG. 10 illustrates example components of baseband circuitry 1010 andradio front end modules (RFEM) 1015 in accordance with variousembodiments. The baseband circuitry 1010 corresponds to the basebandcircuitry 710 and 810 of FIGS. 7 and 8, respectively. The RFEM 1015corresponds to the RFEM 715 and 815 of FIGS. 7 and 8, respectively. Asshown, the RFEMs 1015 may include Radio Frequency (RF) circuitry 1006,front-end module (FEM) circuitry 1008, antenna array 1011 coupledtogether at least as shown.

The baseband circuitry 1010 includes circuitry and/or control logicconfigured to carry out various radio/network protocol and radio controlfunctions that enable communication with one or more radio networks viathe RF circuitry 1006. The radio control functions may include, but arenot limited to, signal modulation/demodulation, encoding/decoding, radiofrequency shifting, etc. In some embodiments, modulation/demodulationcircuitry of the baseband circuitry 1010 may include Fast-FourierTransform (FFT), precoding, or constellation mapping/demappingfunctionality. In some embodiments, encoding/decoding circuitry of thebaseband circuitry 1010 may include convolution, tail-bitingconvolution, turbo, Viterbi, LDPC, and/or polar code encoder/decoderfunctionality. Embodiments of modulation/demodulation andencoder/decoder functionality are not limited to these examples and mayinclude other suitable functionality in other embodiments. The basebandcircuitry 1010 is configured to process baseband signals received from areceive signal path of the RF circuitry 1006 and to generate basebandsignals for a transmit signal path of the RF circuitry 1006. Thebaseband circuitry 1010 is configured to interface with applicationcircuitry 705/805 (see FIGS. 7 and 8) for generation and processing ofthe baseband signals and for controlling operations of the RF circuitry1006. The baseband circuitry 1010 may handle various radio controlfunctions.

The aforementioned circuitry and/or control logic of the basebandcircuitry 1010 may include one or more single or multi-core processors.For example, the one or more processors may include a 3G basebandprocessor 1004A, a 4G/LTE baseband processor 1004B, a 5G/NR basebandprocessor 1004C, or some other baseband processor(s) 1004D for otherexisting generations, generations in development or to be developed inthe future (e.g., 6G, etc.). In other embodiments, some or all of thefunctionality of baseband processors 1004A-D may be included in modulesstored in the memory 1004G and executed via a CPU 1004E. In otherembodiments, some or all of the functionality of baseband processors1004A-D may be provided as hardware accelerators (e.g., FPGAs, ASICs,etc.) loaded with the appropriate bit streams or logic blocks stored inrespective memory cells. In various embodiments, the memory 1004G maystore program code of a real-time OS (RTOS), which when executed by theCPU 1004E (or other baseband processor), is to cause the CPU 1004E (orother baseband processor) to manage resources of the baseband circuitry1010, schedule tasks, etc. Examples of the RTOS may include OperatingSystem Embedded (OSE)™ provided by Enea®, Nucleus RTOS™ provided byMentor Graphics®, Versatile Real-Time Executive (VRTX) provided byMentor Graphics®, ThreadX™ provided by Express Logic®, FreeRTOS, REX OSprovided by Qualcomm®, OKL4 provided by Open Kernel (OK) Labs®, or anyother suitable RTOS, such as those discussed herein. In addition, thebaseband circuitry 1010 includes one or more audio DSPs 1004F. The audioDSP(s) 1004F include elements for compression/decompression and echocancellation and may include other suitable processing elements in otherembodiments.

In some embodiments, each of the processors 1004A-1004E includerespective memory interfaces to send/receive data to/from the memory1004G. The baseband circuitry 1010 may further include one or moreinterfaces to communicatively couple to other circuitries/devices, suchas an interface to send/receive data to/from memory external to thebaseband circuitry 1010; an application circuitry interface tosend/receive data to/from the application circuitry 705/805 of FIGS. 7and 8); an RF circuitry interface to send/receive data to/from RFcircuitry 1006 of FIG. 10; a wireless hardware connectivity interface tosend/receive data to/from one or more wireless hardware elements (e.g.,NFC components, Bluetooth®/Bluetooth® Low Energy components, Wi-Fi®components, and/or the like); and a power management interface tosend/receive power or control signals to/from the PMIC 825.

In alternate embodiments (which may be combined with the above describedembodiments), baseband circuitry 1010 comprises one or more digitalbaseband systems, which are coupled with one another via an interconnectsubsystem and to a CPU subsystem, an audio subsystem, and an interfacesubsystem. The digital baseband subsystems may also be coupled to adigital baseband interface and a mixed-signal baseband subsystem viaanother interconnect subsystem. Each of the interconnect subsystems mayinclude a bus system, point-to-point connections, network-on-chip (NOC)structures, and/or some other suitable bus or interconnect technology,such as those discussed herein. The audio subsystem may include DSPcircuitry, buffer memory, program memory, speech processing acceleratorcircuitry, data converter circuitry such as analog-to-digital anddigital-to-analog converter circuitry, analog circuitry including one ormore of amplifiers and filters, and/or other like components. In anaspect of the present disclosure, baseband circuitry 1010 may includeprotocol processing circuitry with one or more instances of controlcircuitry (not shown) to provide control functions for the digitalbaseband circuitry and/or radio frequency circuitry (e.g., the radiofront end modules 1015).

Although not shown by FIG. 10, in some embodiments, the basebandcircuitry 1010 includes individual processing device(s) to operate oneor more wireless communication protocols (e.g., a “multi-protocolbaseband processor” or “protocol processing circuitry”) and individualprocessing device(s) to implement PHY layer functions. In theseembodiments, the PHY layer functions include the aforementioned radiocontrol functions. In these embodiments, the protocol processingcircuitry operates or implements various protocol layers/entities of oneor more wireless communication protocols. In a first example, theprotocol processing circuitry may operate LTE protocol entities and/or5G/NR protocol entities when the baseband circuitry 1010 and/or RFcircuitry 1006 are part of mmWave communication circuitry or some othersuitable cellular communication circuitry. In the first example, theprotocol processing circuitry would operate MAC, RLC, PDCP, SDAP, RRC,and NAS functions. In a second example, the protocol processingcircuitry may operate one or more IEEE-based protocols when the basebandcircuitry 1010 and/or RF circuitry 1006 are part of a Wi-Ficommunication system. In the second example, the protocol processingcircuitry would operate Wi-Fi MAC and logical link control (LLC)functions. The protocol processing circuitry may include one or morememory structures (e.g., 1004G) to store program code and data foroperating the protocol functions, as well as one or more processingcores to execute the program code and perform various operations usingthe data. The baseband circuitry 1010 may also support radiocommunications for more than one wireless protocol.

The various hardware elements of the baseband circuitry 1010 discussedherein may be implemented, for example, as a solder-down substrateincluding one or more integrated circuits (ICs), a single packaged ICsoldered to a main circuit board or a multi-chip module containing twoor more ICs. In one example, the components of the baseband circuitry1010 may be suitably combined in a single chip or chipset, or disposedon a same circuit board. In another example, some or all of theconstituent components of the baseband circuitry 1010 and RF circuitry1006 may be implemented together such as, for example, a system on achip (SoC) or System-in-Package (SiP). In another example, some or allof the constituent components of the baseband circuitry 1010 may beimplemented as a separate SoC that is communicatively coupled with andRF circuitry 1006 (or multiple instances of RF circuitry 1006). In yetanother example, some or all of the constituent components of thebaseband circuitry 1010 and the application circuitry 705/805 may beimplemented together as individual SoCs mounted to a same circuit board(e.g., a “multi-chip package”).

In some embodiments, the baseband circuitry 1010 may provide forcommunication compatible with one or more radio technologies. Forexample, in some embodiments, the baseband circuitry 1010 may supportcommunication with an E-UTRAN or other WMAN, a WLAN, a WPAN. Embodimentsin which the baseband circuitry 1010 is configured to support radiocommunications of more than one wireless protocol may be referred to asmulti-mode baseband circuitry.

RF circuitry 1006 may enable communication with wireless networks usingmodulated electromagnetic radiation through a non-solid medium. Invarious embodiments, the RF circuitry 1006 may include switches,filters, amplifiers, etc. to facilitate the communication with thewireless network. RF circuitry 1006 may include a receive signal path,which may include circuitry to down-convert RF signals received from theFEM circuitry 1008 and provide baseband signals to the basebandcircuitry 1010. RF circuitry 1006 may also include a transmit signalpath, which may include circuitry to up-convert baseband signalsprovided by the baseband circuitry 1010 and provide RF output signals tothe FEM circuitry 1008 for transmission.

In some embodiments, the receive signal path of the RF circuitry 1006may include mixer circuitry 1006 a, amplifier circuitry 1006 b andfilter circuitry 1006 c. In some embodiments, the transmit signal pathof the RF circuitry 1006 may include filter circuitry 1006 c and mixercircuitry 1006 a. RF circuitry 1006 may also include synthesizercircuitry 1006 d for synthesizing a frequency for use by the mixercircuitry 1006 a of the receive signal path and the transmit signalpath. In some embodiments, the mixer circuitry 1006 a of the receivesignal path may be configured to down-convert RF signals received fromthe FEM circuitry 1008 based on the synthesized frequency provided bysynthesizer circuitry 1006 d. The amplifier circuitry 1006 b may beconfigured to amplify the down-converted signals and the filtercircuitry 1006 c may be a low-pass filter (LPF) or band-pass filter(BPF) configured to remove unwanted signals from the down-convertedsignals to generate output baseband signals. Output baseband signals maybe provided to the baseband circuitry 1010 for further processing. Insome embodiments, the output baseband signals may be zero-frequencybaseband signals, although this is not a requirement. In someembodiments, mixer circuitry 1006 a of the receive signal path maycomprise passive mixers, although the scope of the embodiments is notlimited in this respect.

In some embodiments, the mixer circuitry 1006 a of the transmit signalpath may be configured to up-convert input baseband signals based on thesynthesized frequency provided by the synthesizer circuitry 1006 d togenerate RF output signals for the FEM circuitry 1008. The basebandsignals may be provided by the baseband circuitry 1010 and may befiltered by filter circuitry 1006 c.

In some embodiments, the mixer circuitry 1006 a of the receive signalpath and the mixer circuitry 1006 a of the transmit signal path mayinclude two or more mixers and may be arranged for quadraturedownconversion and upconversion, respectively. In some embodiments, themixer circuitry 1006 a of the receive signal path and the mixercircuitry 1006 a of the transmit signal path may include two or moremixers and may be arranged for image rejection (e.g., Hartley imagerejection). In some embodiments, the mixer circuitry 1006 a of thereceive signal path and the mixer circuitry 1006 a of the transmitsignal path may be arranged for direct downconversion and directupconversion, respectively. In some embodiments, the mixer circuitry1006 a of the receive signal path and the mixer circuitry 1006 a of thetransmit signal path may be configured for super-heterodyne operation.

In some embodiments, the output baseband signals and the input basebandsignals may be analog baseband signals, although the scope of theembodiments is not limited in this respect. In some alternateembodiments, the output baseband signals and the input baseband signalsmay be digital baseband signals. In these alternate embodiments, the RFcircuitry 1006 may include analog-to-digital converter (ADC) anddigital-to-analog converter (DAC) circuitry and the baseband circuitry1010 may include a digital baseband interface to communicate with the RFcircuitry 1006.

In some dual-mode embodiments, a separate radio IC circuitry may beprovided for processing signals for each spectrum, although the scope ofthe embodiments is not limited in this respect.

In some embodiments, the synthesizer circuitry 1006 d may be afractional-N synthesizer or a fractional N/N+1 synthesizer, although thescope of the embodiments is not limited in this respect as other typesof frequency synthesizers may be suitable. For example, synthesizercircuitry 1006 d may be a delta-sigma synthesizer, a frequencymultiplier, or a synthesizer comprising a phase-locked loop with afrequency divider.

The synthesizer circuitry 1006 d may be configured to synthesize anoutput frequency for use by the mixer circuitry 1006 a of the RFcircuitry 1006 based on a frequency input and a divider control input.In some embodiments, the synthesizer circuitry 1006 d may be afractional N/N+1 synthesizer.

In some embodiments, frequency input may be provided by a voltagecontrolled oscillator (VCO), although that is not a requirement. Dividercontrol input may be provided by either the baseband circuitry 1010 orthe application circuitry 705/805 depending on the desired outputfrequency. In some embodiments, a divider control input (e.g., N) may bedetermined from a look-up table based on a channel indicated by theapplication circuitry 705/805.

Synthesizer circuitry 1006 d of the RF circuitry 1006 may include adivider, a delay-locked loop (DLL), a multiplexer and a phaseaccumulator. In some embodiments, the divider may be a dual modulusdivider (DMD) and the phase accumulator may be a digital phaseaccumulator (DPA). In some embodiments, the DMD may be configured todivide the input signal by either N or N+1 (e.g., based on a carry out)to provide a fractional division ratio. In some example embodiments, theDLL may include a set of cascaded, tunable, delay elements, a phasedetector, a charge pump and a D-type flip-flop. In these embodiments,the delay elements may be configured to break a VCO period up into Ndequal packets of phase, where Nd is the number of delay elements in thedelay line. In this way, the DLL provides negative feedback to helpensure that the total delay through the delay line is one VCO cycle.

In some embodiments, synthesizer circuitry 1006 d may be configured togenerate a carrier frequency as the output frequency, while in otherembodiments, the output frequency may be a multiple of the carrierfrequency (e.g., twice the carrier frequency, four times the carrierfrequency) and used in conjunction with quadrature generator and dividercircuitry to generate multiple signals at the carrier frequency withmultiple different phases with respect to each other. In someembodiments, the output frequency may be a LO frequency (fLO). In someembodiments, the RF circuitry 1006 may include an IQ/polar converter.

FEM circuitry 1008 may include a receive signal path, which may includecircuitry configured to operate on RF signals received from antennaarray 1011, amplify the received signals and provide the amplifiedversions of the received signals to the RF circuitry 1006 for furtherprocessing. FEM circuitry 1008 may also include a transmit signal path,which may include circuitry configured to amplify signals fortransmission provided by the RF circuitry 1006 for transmission by oneor more of antenna elements of antenna array 1011. In variousembodiments, the amplification through the transmit or receive signalpaths may be done solely in the RF circuitry 1006, solely in the FEMcircuitry 1008, or in both the RF circuitry 1006 and the FEM circuitry1008.

In some embodiments, the FEM circuitry 1008 may include a TX/RX switchto switch between transmit mode and receive mode operation. The FEMcircuitry 1008 may include a receive signal path and a transmit signalpath. The receive signal path of the FEM circuitry 1008 may include anLNA to amplify received RF signals and provide the amplified received RFsignals as an output (e.g., to the RF circuitry 1006). The transmitsignal path of the FEM circuitry 1008 may include a power amplifier (PA)to amplify input RF signals (e.g., provided by RF circuitry 1006), andone or more filters to generate RF signals for subsequent transmissionby one or more antenna elements of the antenna array 1011.

The antenna array 1011 comprises one or more antenna elements, each ofwhich is configured convert electrical signals into radio waves totravel through the air and to convert received radio waves intoelectrical signals. For example, digital baseband signals provided bythe baseband circuitry 1010 is converted into analog RF signals (e.g.,modulated waveform) that will be amplified and transmitted via theantenna elements of the antenna array 1011 including one or more antennaelements (not shown). The antenna elements may be omnidirectional,direction, or a combination thereof. The antenna elements may be formedin a multitude of arranges as are known and/or discussed herein. Theantenna array 1011 may comprise microstrip antennas or printed antennasthat are fabricated on the surface of one or more printed circuitboards. The antenna array 1011 may be formed in as a patch of metal foil(e.g., a patch antenna) in a variety of shapes, and may be coupled withthe RF circuitry 1006 and/or FEM circuitry 1008 using metal transmissionlines or the like.

Processors of the application circuitry 705/805 and processors of thebaseband circuitry 1010 may be used to execute elements of one or moreinstances of a protocol stack. For example, processors of the basebandcircuitry 1010, alone or in combination, may be used execute Layer 3,Layer 2, or Layer 1 functionality, while processors of the applicationcircuitry 705/805 may utilize data (e.g., packet data) received fromthese layers and further execute Layer 4 functionality (e.g., TCP andUDP layers). As referred to herein, Layer 3 may comprise a RRC layer,described in further detail below. As referred to herein, Layer 2 maycomprise a MAC layer, an RLC layer, and a PDCP layer, described infurther detail below. As referred to herein, Layer 1 may comprise a PHYlayer of a UE/RAN node, described in further detail infra.

FIG. 11 illustrates various protocol functions that may be implementedin a wireless communication device according to various embodiments. Inparticular, FIG. 11 includes an arrangement 1100 showinginterconnections between various protocol layers/entities. The followingdescription of FIG. 11 is provided for various protocol layers/entitiesthat operate in conjunction with the 5G/NR system standards and LTEsystem standards, but some or all of the aspects of FIG. 11 may beapplicable to other wireless communication network systems as well.

The protocol layers of arrangement 1100 may include one or more of PHY1110, MAC 1120, RLC 1130, PDCP 1140, SDAP 1147, RRC 1155, and NAS layer1157, in addition to other higher layer functions not illustrated. Theprotocol layers may include one or more service access points (e.g.,items 1159, 1156, 1150, 1149, 1145, 1135, 1125, and 1115 in FIG. 11)that may provide communication between two or more protocol layers.

The PHY 1110 may transmit and receive physical layer signals 1105 thatmay be received from or transmitted to one or more other communicationdevices. The physical layer signals 1105 may comprise one or morephysical channels, such as those discussed herein. The PHY 1110 mayfurther perform link adaptation or adaptive modulation and coding (AMC),power control, cell search (e.g., for initial synchronization andhandover purposes), and other measurements used by higher layers, suchas the RRC 1155. The PHY 1110 may still further perform error detectionon the transport channels, forward error correction (FEC)coding/decoding of the transport channels, modulation/demodulation ofphysical channels, interleaving, rate matching, mapping onto physicalchannels, and MIMO antenna processing. In embodiments, an instance ofPHY 1110 may process requests from and provide indications to aninstance of MAC 1120 via one or more PHY-SAP 1115. According to someembodiments, requests and indications communicated via PHY-SAP 1115 maycomprise one or more transport channels.

Instance(s) of MAC 1120 may process requests from, and provideindications to, an instance of RLC 1130 via one or more MAC-SAPs 1125.These requests and indications communicated via the MAC-SAP 1125 maycomprise one or more logical channels. The MAC 1120 may perform mappingbetween the logical channels and transport channels, multiplexing of MACSDUs from one or more logical channels onto TBs to be delivered to PHY1110 via the transport channels, de-multiplexing MAC SDUs to one or morelogical channels from TBs delivered from the PHY 1110 via transportchannels, multiplexing MAC SDUs onto TBs, scheduling informationreporting, error correction through HARQ, and logical channelprioritization.

Instance(s) of RLC 1130 may process requests from and provideindications to an instance of PDCP 1140 via one or more radio linkcontrol service access points (RLC-SAP) 1135. These requests andindications communicated via RLC-SAP 1135 may comprise one or more RLCchannels. The RLC 1130 may operate in a plurality of modes of operation,including: Transparent Mode™, Unacknowledged Mode (UM), and AcknowledgedMode (AM). The RLC 1130 may execute transfer of upper layer protocoldata units (PDUs), error correction through automatic repeat request(ARQ) for AM data transfers, and concatenation, segmentation andreassembly of RLC SDUs for UM and AM data transfers. The RLC 1130 mayalso execute re-segmentation of RLC data PDUs for AM data transfers,reorder RLC data PDUs for UM and AM data transfers, detect duplicatedata for UM and AM data transfers, discard RLC SDUs for UM and AM datatransfers, detect protocol errors for AM data transfers, and perform RLCre-establishment.

Instance(s) of PDCP 1140 may process requests from and provideindications to instance(s) of RRC 1155 and/or instance(s) of SDAP 1147via one or more packet data convergence protocol service access points(PDCP-SAP) 1145. These requests and indications communicated viaPDCP-SAP 1145 may comprise one or more radio bearers. The PDCP 1140 mayexecute header compression and decompression of IP data, maintain PDCPSequence Numbers (SNs), perform in-sequence delivery of upper layer PDUsat re-establishment of lower layers, eliminate duplicates of lower layerSDUs at re-establishment of lower layers for radio bearers mapped on RLCAM, cipher and decipher control plane data, perform integrity protectionand integrity verification of control plane data, control timer-baseddiscard of data, and perform security operations (e.g., ciphering,deciphering, integrity protection, integrity verification, etc.).

Instance(s) of SDAP 1147 may process requests from and provideindications to one or more higher layer protocol entities via one ormore SDAP-SAP 1149. These requests and indications communicated viaSDAP-SAP 1149 may comprise one or more QoS flows. The SDAP 1147 may mapQoS flows to DRBs, and vice versa, and may also mark QFIs in DL and ULpackets. A single SDAP entity 1147 may be configured for an individualPDU session. In the UL direction, the NG-RAN 110 may control the mappingof QoS Flows to DRB(s) in two different ways, reflective mapping orexplicit mapping. For reflective mapping, the SDAP 1147 of a UE 101 maymonitor the QFIs of the DL packets for each DRB, and may apply the samemapping for packets flowing in the UL direction. For a DRB, the SDAP1147 of the UE 101 may map the UL packets belonging to the QoS flows(s)corresponding to the QoS flow ID(s) and PDU session observed in the DLpackets for that DRB. To enable reflective mapping, the NG-RAN 610 maymark DL packets over the Uu interface with a QoS flow ID. The explicitmapping may involve the RRC 1155 configuring the SDAP 1147 with anexplicit QoS flow to DRB mapping rule, which may be stored and followedby the SDAP 1147. In embodiments, the SDAP 1147 may only be used in NRimplementations and may not be used in LTE implementations.

The RRC 1155 may configure, via one or more management service accesspoints (M-SAP), aspects of one or more protocol layers, which mayinclude one or more instances of PHY 1110, MAC 1120, RLC 1130, PDCP 1140and SDAP 1147. In embodiments, an instance of RRC 1155 may processrequests from and provide indications to one or more NAS entities 1157via one or more RRC-SAPs 1156. The main services and functions of theRRC 1155 may include broadcast of system information (e.g., included inMIBs or SIBs related to the NAS), broadcast of system informationrelated to the access stratum (AS), paging, establishment, maintenanceand release of an RRC connection between the UE 101 and RAN 110 (e.g.,RRC connection paging, RRC connection establishment, RRC connectionmodification, and RRC connection release), establishment, configuration,maintenance and release of point to point Radio Bearers, securityfunctions including key management, inter-RAT mobility, and measurementconfiguration for UE measurement reporting. The MIBs and SIBs maycomprise one or more IEs, which may each comprise individual data fieldsor data structures.

According to various embodiments, RRC 1155 is used to configure the UE101 with specific parameters, such as specific PUCCH parameters, CSI-RSparameters, SRS parameters, and/or other like parameters. For example,the RRC 1155 of a RAN node 111 may transmit a suitable RRC message(e.g., an RRC connection establishment message, RRC connectionreconfiguration message, or the like) to the UE 101, where the RRCmessage includes one or more IEs, which is a structural elementcontaining one or more fields where each field includes parameters,content, and/or data. The parameters, content, and/or data included inthe one or more fields of the IEs are used to configure the UE 101 tooperate in a particular manner. In some embodiments, one or more PUCCHconfiguration (PUCCH-Config) IEs are included in such an RRC message,which are used to configure UE specific PUCCH parameters applicable to arespective BWP. An example PUCCH-Config IE is shown by table 2 and table3 shows field descriptions for the fields of the PUCCH-Config IE.

TABLE 2 PUCCH-Config information element -- ASN1START --TAG-PUCCH-CONFIG-START PUCCH-Config ::= SEQUENCE {resourceSetToAddModList SEQUENCE (SIZE (1..maxNrofPUCCH- ResourceSets))OF PUCCH-ResourceSet OPTIONAL, -- Need N resourceSetToReleaseListSEQUENCE (SIZE (1..maxNrofPUCCH- ResourceSets)) OF PUCCH-ResourceSetIdOPTIONAL, -- Need N resourceToAddModList SEQUENCE (SIZE(1..maxNrofPUCCH- Resources)) OF PUCCH-Resource OPTIONAL, -- Need NresourceToReleaseList SEQUENCE (SIZE (1..maxNrofPUCCH- Resources)) OFPUCCH-ResourceId OPTIONAL, -- Need N format1 SetupRelease {PUCCH-FormatConfig } OPTIONAL, -- Need M format2 SetupRelease {PUCCH-FormatConfig } OPTIONAL, -- Need M format3 SetupRelease {PUCCH-FormatConfig } OPTIONAL, -- Need M format4 SetupRelease {PUCCH-FormatConfig } OPTIONAL, -- Need MschedulingRequestResourceToAddModList SEQUENCE (SIZE(1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfig  OPTIONAL,-- Need N schedulingRequestResourceToReleaseList SEQUENCE (SIZE(1..maxNrofSR-Resources)) OF SchedulingRequestResourceId  OPTIONAL, --Need N multi-CSI-PUCCH-ResourceList SEQUENCE (SIZE (1..2)) OF PUCCH-ResourceId OPTIONAL, -- Need M dl-DataToUL-ACK SEQUENCE (SIZE (1..8)) OFINTEGER (0..15) OPTIONAL, -- Need M spatialRelationInfoToAddModListSEQUENCE (SIZE (1..maxNrofSpatialRelationInfos)) OFPUCCH-SpatialRelationInfo OPTIONAL, -- Need NspatialRelationInfoToReleaseList SEQUENCE (SIZE(1..maxNrofSpatialRelationInfos)) OF PUCCH-SpatialRelationInfoIdOPTIONAL, -- Need N pucch-PowerControl PUCCH-PowerControl OPTIONAL, --Need M ... } PUCCH-FormatConfig ::= SEQUENCE { interslotFrequencyHoppingENUMERATED {enabled} OPTIONAL, -- Need R additionalDMRS ENUMERATED{true} OPTIONAL, -- Need R maxCodeRate PUCCH-MaxCodeRate OPTIONAL, --Need R nrofSlots ENUMERATED {n2,n4,n8} OPTIONAL, -- Need S pi2BPSKENUMERATED {enabled} OPTIONAL, -- Need R simultaneousHARQ-ACK-CSIENUMERATED {true} OPTIONAL -- Need R } PUCCH-MaxCodeRate ::= ENUMERATED{zeroDot08, zeroDot15, zeroDot25, zeroDot35, zeroDot45, zeroDot60,zeroDot80} -- A set with one or more PUCCH resources PUCCH-ResourceSet::= SEQUENCE { pucch-ResourceSetId PUCCH-ResourceSetId, resourceListSEQUENCE (SIZE (1..maxNrofPUCCH- ResourcesPerSet)) OF PUCCH-ResourceId,maxPayloadMinus1 INTEGER (4..256) OPTIONAL -- Need R }PUCCH-ResourceSetId ::= INTEGER (0..maxNrofPUCCH-ResourceSets−1)PUCCH-Resource ::= SEQUENCE { pucch-ResourceId PUCCH-ResourceId,startingPRB PRB-Id, intraSlotFrequencyHopping ENUMERATED { enabled }OPTIONAL, -- Need R secondHopPRB PRB-Id OPTIONAL, -- Need R formatCHOICE { format0 PUCCH-format0, format1 PUCCH-format1, format2PUCCH-format2, format3 PUCCH-format3, format4 PUCCH-format4 } }PUCCH-ResourceId ::= INTEGER (0..maxNrofPUCCH-Resources−1) PUCCH-format0::= SEQUENCE { initialCyclicShift INTEGER(0..11), nrofSymbols INTEGER(1..2), startingSymbolIndex INTEGER(0..13) } PUCCH-format1 ::= SEQUENCE{ initialCyclicShift INTEGER(0..11), nrofSymbols INTEGER (4..14),startingSymbolIndex INTEGER(0..10), timeDomainOCC INTEGER(0..6) }PUCCH-format2 ::= SEQUENCE { nrofPRBs INTEGER (1..16), nrofSymbolsINTEGER (1..2), startingSymbolIndex INTEGER(0..13) } PUCCH-format3 ::=SEQUENCE { nrofPRBs INTEGER (1..16), nrofSymbols INTEGER (4..14),startingSymbolIndex INTEGER(0..10) } PUCCH-format4 ::= SEQUENCE {nrofSymbols INTEGER (4..14), occ-Length ENUMERATED {n2,n4}, occ-IndexENUMERATED {n0,n1,n2,n3}, startingSymbolIndex INTEGER(0..10) } --TAG-PUCCH-CONFIG-STOP -- ASN1STOP

TABLE 3 PUCCH-Config field descriptions dl-DataToUL-ACK List of timingfor given PDSCH to the DL ACK. format1 Parameters that are common forall PUCCH resources of format 1. format2 Parameters that are common forall PUCCH resources of format 2. format3 Parameters that are common forall PUCCH resources of format 3. format4. Parameters that are common forall PUCCH resources of format 4 resourceSetToAddModList Lists for addingand releasing PUCCH resource sets resourceToAddModList,resourceToReleaseList Lists for adding and releasing PUCCH resourcesapplicable for the UL BWP and serving cell in which the PUCCH-Config isdefined. The resources defined herein are referred to from other partsof the configuration to determine which resource the UE shall use forwhich report. spatialRelationInfoToAddModList Configuration of thespatial relation between a reference RS and PUCCH. Reference RS can beSSB/CSI-RS/SRS. If the list has more than one element, MAC-CE selects asingle element. dl-DataToUL-ACK List of timing for given PDSCH to the DLACK PUCCH-format3 field descriptions nrofPRBs The supported values are1, 2, 3, 4, 5, 6, 8, 9, 10, 12, 15 and 16. PUCCH-FormatConfig fielddescriptions additionalDMRS If the field is present, the UE enables 2DMRS symbols per hop of a PUCCH Format 3 or 4 if both hops are more thanX symbols when FH is enabled (X = 4). And it enables 4 DMRS symbols fora PUCCH Format 3 or 4 with more than 2X + 1 symbols when FH is disabled(X = 4). The field is not applicable for format 1 and 2.interslotFrequencyHopping If the field is present, the UE enablesinter-slot frequency hopping when PUCCH Format 1, 3 or 4 is repeatedover multiple slots. For long PUCCH over multiple slots, the intra andinter slot frequency hopping cannot be enabled at the same time for aUE. The field is not applicable for format 2. maxCodeRate Max codingrate to determine how to feedback UCI on PUCCH for format 2, 3 or 4. Thefield is not applicable for format 1. nrofSlots Number of slots with thesame PUCCH F1, F3 or F4. When the field is absent the UE applies thevalue n1. The field is not applicable for format 2. pi2BPSK If the fieldis present, the UE uses pi/2 BPSK for UCI symbols instead of QPSK forPUCCH. The field is not applicable for format 1 and 2.simultaneousHARQ-ACK-CSI If the field is present, the UE usessimultaneous transmission of CSI and HARQ-ACK feedback with or withoutSR with PUCCH Format 2, 3 or 4. When the field is absent the UE appliesthe value OFF The field is not applicable for format 1. PUCCH-Resourcefield descriptions format Selection of the PUCCH format (format 0-4) andformat-specific parameters. format0 and format1 are only allowed for aresource in a first PUCCH resource set. format2, format3 and format4 areonly allowed for a resource in non-first PUCCH resource set.intraSlotFrequencyHopping Enabling intra-slot frequency hopping,applicable for all types of PUCCH formats. For long PUCCH over multipleslots, the intra and inter slot frequency hopping cannot be enabled atthe same time for a UE. pucch-ResourceId Identifier of the PUCCHresource. secondHopPRB Index of first PRB after frequency hopping (forsecond hop) of PUCCH. This value is applicable for intra-slot frequencyhopping. PUCCH-ResourceSet field descriptions maxPayloadMinus1 Maximumnumber of payload bits minus 1 that the UE may transmit using this PUCCHresource set. In a PUCCH occurrence, the UE chooses the first of itsPUCCH-ResourceSet which supports the number of bits that the UE wants totransmit. The field is not present in the first set (Set0) since themaximum Size of Set0 is specified to be 3 bits. The field is not presentin the last configured set since the UE derives its maximum payload sizeas specified in TS 38.213 [13]. This field can take integer values thatare multiples of 4 (see TS 38.213 [13], clause 9.2). resourceList PUCCHresources of format0 and format1 are only allowed in the first PUCCHresource set, i.e., in a PUCCH-ResourceSet with pucch-ResourceSetId = 0.This set may contain between 1 and 32 resources. PUCCH resources offormat2, format3 and format4 are only allowed in a PUCCH- ResourceSetwith pucch-ResourceSetId > 0. If present, these sets contain between 1and 8 resources each. The UE chooses a PUCCH-Resource from this list asspecified in TS 38.213 [13], clause 9.2.3. Note that this list containsonly a list of resource IDs. The actual resources are configured inPUCCH- Config.

In the examples of tables 2-3, the PUCCH-Config IE includes aPUCCH-SpatialRelationInfo IE, which is used to configure the spatialsetting for PUCCH transmission and the parameters for PUCCH powercontrol. An example PUCCH-SpatialRelationInfo IE is shown by table 4,and PUCCH-SpatialRelationInfo field descriptions are shown by table 5.

TABLE 4 PUCCH-SpatialRelationInfo information element -- ASN1START --TAG-PUCCH-SPATIALRELATIONINFO-START PUCCH-SpatialRelationInfo ::=SEQUENCE { pucch-SpatialRelationInfoId PUCCH-SpatialRelationInfoId,servingCellId ServCellIndex OPTIONAL, -- Need S referenceSignal CHOICE {ssb-Index SSB-Index, csi-RS-Index NZP-CSI-RS-ResourceId, srs SEQUENCE {resource SRS- ResourceId, uplinkBWP BWP-Id } },pucch-PathlossReferenceRS-Id PUCCH-PathlossReferenceRS-Id, p0-PUCCH-IdP0-PUCCH-Id, closedLoopIndex ENUMERATED { i0, i1 } }PUCCH-SpatialRelationInfoId ::= INTEGER (1..maxNrofSpatialRelationInfos)-- TAG-PUCCH-SPATIALRELATIONINFO-STOP -- ASN1STOP

TABLE 5 PUCCH-SpatialRelationInfo field descriptions servingCellId Ifthe field is absent, the UE applies the ServCellId of the serving cellin which this PUCCH-SpatialRelationInfo is configured

In some embodiments, a CSI measurement configuration (CSI-MeasConfig) IEis used to configure CSI-RS (reference signals) belonging to a servingcell in which CSI-MeasConfig is included, channel state information(CSI) reports to be transmitted on PUCCH on the serving cell in whichCSI-MeasConfig is included, and/or CSI reports on PUSCH triggered by DCIreceived on the serving cell in which CSI-MeasConfig is included. Anexample CSI-MeasConfig IE is shown by table 6 and CSI-MeasConfig fielddescriptions are given by table 7.

TABLE 6 CSI-MeasConfig information element -- ASN1START --TAG-CSI-MEAS-CONFIG-START CSI-MeasConfig ::= SEQUENCE {nzp-CSI-RS-ResourceToAddModList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-Resources)) OF NZP-CSI-RS-Resource OPTIONAL, -- Need Nnzp-CSI-RS-ResourceToReleaseList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-Resources)) OF NZP-CSI-RS-ResourceId OPTIONAL, -- Need Nnzp-CSI-RS-ResourceSetToAddModList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSets)) OF NZP-CSI-RS-ResourceSet OPTIONAL, -- Need Nnzp-CSI-RS-ResourceSetToReleaseList SEQUENCE (SIZE(1..maxNrofNZP-CSI-RS- ResourceSets)) OF NZP-CSI-RS-ResourceSetIdOPTIONAL, -- Need N csi-IM-ResourceToAddModList SEQUENCE (SIZE(1..maxNrofCSI-IM-Resources)) OF CSI-IM-Resource  OPTIONAL, -- Need Ncsi-IM-ResourceToReleaseList SEQUENCE (SIZE(1..maxNrofCSI-IM-Resources)) OF CSI-IM-ResourceId  OPTIONAL, -- Need Ncsi-IM-ResourceSetToAddModList SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSets)) OF CSI-IM-ResourceSet  OPTIONAL, -- Need Ncsi-IM-ResourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSets)) OF CSI-IM-ResourceSetId  OPTIONAL, -- Need Ncsi-SSB-ResourceSetToAddModList SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSets)) OF CSI-SSB-ResourceSet OPTIONAL, -- Need Ncsi-SSB-ResourceSetToAddReleaseList SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSets)) OF CSI-SSB-ResourceSetId OPTIONAL, -- Need Ncsi-ResourceConfigToAddModList SEQUENCE (SIZE (1..maxNrofCSI-ResourceConfigurations)) OF CSI-ResourceConfig OPTIONAL, -- Need Ncsi-ResourceConfigToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-ResourceConfigurations)) OF CSI-ResourceConfigId OPTIONAL, -- Need Ncsi-ReportConfigToAddModList SEQUENCE (SIZE (1..maxNrofCSI-ReportConfigurations)) OF CSI-ReportConfig OPTIONAL, -- Need Ncsi-ReportConfigToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-ReportConfigurations)) OF CSI-ReportConfigId OPTIONAL, -- Need NreportTriggerSize INTEGER (0..6) OPTIONAL, -- Need MaperiodicTriggerStateList SetupRelease { CSI-AperiodicTriggerStateList } OPTIONAL, -- Need M semiPersistentOnPUSCH-TriggerStateList SetupRelease { CSI- SemiPersistentOnPUSCH-TriggerStateList } OPTIONAL,-- Need M ... } -- TAG-CSI-MEAS-CONFIG-STOP -- ASN1STOP

TABLE 7 CSI-MeasConfig field descriptions aperiodicTriggerStateListContains trigger states for dynamically selecting one or more aperiodicand semi-persistent reporting configurations and/or triggering one ormore aperiodic CSI-RS resource sets for channel and/or interferencemeasurement. FFS: How to address the MAC-CE configuration.csi-IM-ResourceSetToAddModList Pool of CSI-IM-ResourceSet which can bereferred to from CSI-ResourceConfig or from MAC CEs.csi-IM-ResourceToAddModList Pool of CSI-IM-Resource which can bereferred to from CSI-IM-ResourceSet. csi-ReportConfigToAddModListConfigured CSI report settings. csi-ResourceConfigToAddModListConfigured CSI resource settings. csi-SSB-ResourceSetToAddModList Poolof CSI-SSB-ResourceSet which can be referred to from CSI-ResourceConfig.nzp-CSI-RS-ResourceSetToAddModList Pool of NZP-CSI-RS-ResourceSet whichcan be referred to from CSI-ResourceConfig or from MAC CEs.nzp-CSI-RS-ResourceToAddModList Pool of NZP-CSI-RS-Resource which can bereferred to from NZP-CSI-RS-ResourceSet. reportTriggerSize Size of CSIrequest field in DCI (bits).

As shown by tables 6 and 7, the CSI-MeasConfig IE may include one ormore csi-ResourceConfigToAddModList IEs, which indicates configured CSIresource settings via one or more CSI-ResourceConfig IEs. TheCSI-ResourceConfig IE defines a group of one or moreNZP-CSI-PS-ResourceSet, CSI-IM-ResourceSet, and/or CSI-SSB-ResourceSet.An example C CSI-ResourceConfig IE is shown by table 8 andCSI-ResourceConfig field descriptions are given by table 9.

TABLE 8 CSI-ResourceConfig information element -- ASN1START --TAG-CSI-RESOURCECONFIG-START CSI-ResourceConfig ::= SEQUENCE {csi-ResourceConfigId CSI-ResourceConfigId, csi-RS-ResourceSetList CHOICE{ nzp-CSI-RS-SSB SEQUENCE { nzp-CSI-RS-ResourceSetList SEQUENCE (SIZE(1..maxNrofNZP-CSI-RS- ResourceSetsPerConfig)) OFNZP-CSI-RS-ResourceSetId OPTIONAL, -- Need R csi-SSB-ResourceSetListSEQUENCE (SIZE (1..maxNrofCSI-SSB- ResourceSetsPerConfig)) OFCSI-SSB-ResourceSetId OPTIONAL -- Need R }, csi-IM-ResourceSetListSEQUENCE (SIZE (1..maxNrofCSI-IM- ResourceSetsPerConfig)) OFCSI-IM-ResourceSet Id }, bwp-Id BWP-Id, resourceType ENUMERATED {aperiodic, semiPersistent, periodic }, ... } --TAG-CSI-RESOURCECONFIG-STOP -- ASN1STOP

TABLE 9 CSI-ResourceConfig field descriptions bwp-Id The DL BWP whichthe CSI-RS associated with this CSI-ResourceConfig are located in.csi-ResourceConfigId Used in CSI-ReportConfig to refer to an instance ofCSI-ResourceConfig csi-RS-ResourceSetList Contains up tomaxNrofNZP-CSI-RS-ResourceSetsPerConfig resource sets ifResourceConfigType is ‘aperiodic’ and 1 otherwise.csi-SSB-ResourceSetList List of SSB resources used for beam measurementand reporting in a resource set. resourceType Time domain behavior ofresource configuration. It does not apply to resources provided in thecsi- SSB-ResourceSetList. bwp-Id The DL BWP which the CSI-RS associatedwith this CSI-ResourceConfig are located in. csi-ResourceConfigId Usedin CSI-ReportConfig to refer to an instance of CSI-ResourceConfigcsi-RS-ResourceSetList Contains up tomaxNrofNZP-CSI-RS-ResourceSetsPerConfig resource sets ifResourceConfigType is ‘aperiodic’ and 1 otherwise.csi-SSB-ResourceSetList List of SSB resources used for beam measurementand reporting in a resource set.

As shown by tables 8 and 9, the CSI-MeasConfig IE may include one ormore nzp-CSI-RS-ResourceSetToAddModList IEs, which indicate one or moreNZP CSI-RSs resource sets indicated by respective NZP-CSI-RS-ResourceSetIEs. Each of the NZP-CSI-RS-ResourceSet IEs may indicate one or moreNZP-CSI-RS-Resources. Each NZP-CSI-RS-ResourceSet IE is a set of NZPCSI-RS resources, which may be indicated by their IDs, and set-specificparameters. An example NZP-CSI-RS-ResourceSet IE is shown by table 10,and field descriptions for the NZP-CSI-RS-ResourceSet are shown by table11.

TABLE 10 NZP-CSI-RS-ResourceSet information element -- ASN1START --TAG-NZP-CSI-RS-RESOURCESET-START NZP-CSI-RS-ResourceSet ::= SEQUENCE {nzp-CSI-ResourceSetId NZP-CSI-RS-ResourceSetId, nzp-CSI-RS-ResourcesSEQUENCE (SIZE (1..maxNrofNZP-CSI-RS- ResourcesPerSet)) OFNZP-CSI-RS-ResourceId, repetition ENUMERATED { on, off } OPTIONAL, --Need S aperiodicTriggeringOffset INTEGER(0..6) OPTIONAL, -- Need Strs-Info ENUMERATED {true} OPTIONAL, -- Need R ... } --TAG-NZP-CSI-RS-RESOURCESET-STOP -- ASN1STOP

TABLE 11 NZP-CSI-RS-ResourceSet field descriptionsaperiodicTriggeringOffset Offset X between the slot containing the DCIthat triggers a set of aperiodic NZP CSI-RS resources and the slot inwhich the CSI-RS resource set is transmitted. The value 0 corresponds to0 slots, value 1 corresponds to 1 slot, value 2 corresponds to 2 slots,value 3 corresponds to 3 slots, value 4 corresponds to 4 slots, value 5corresponds to 16 slots, value 6 corresponds to 24 slots. When the fieldis absent the UE applies the value 0. nzp-CSI-RS-ResourcesNZP-CSI-RS-Resources associated with this NZP-CSI-RS resource set. ForCSI, there are at most 8 NZP CSI RS resources per resource setrepetition Indicates whether repetition is on/off. If the field is setto ‘OFF’ or if the field is absent, the UE may not assume that theNZP-CSI-RS resources within the resource set are transmitted with thesame downlink spatial domain transmission filter and with same NrofPortsin every symbol (see TS 38.214 [19], clauses 5.2.2.3.1 and 5.1.6.1.2).Can only be configured for CSI-RS resource sets which are associatedwith CSI-ReportConfig with report of L1 RSRP or “no report” trs-InfoIndicates that the antenna port for all NZP-CSI-RS resources in theCSI-RS resource set is same. If the field is absent or released the UEapplies the value “false”

The NZP-CSI-RS-Resource IE is used to configure Non-Zero-Power (NZP)CSI-RS transmitted in the cell where the IE is included, which the UEmay be configured to measure on. An example NZP-CSI-RS-Resource IE isshown by table 12, and field descriptions for the NZP-CSI-RS-Resourceare shown by table 13.

TABLE 12 NZP-CSI-RS-Resource information element -- ASN1START --TAG-NZP-CSI-RS-RESOURCE-START NZP-CSI-RS-Resource ::= SEQUENCE {nzp-CSI-RS-ResourceId NZP-CSI-RS-ResourceId, resourceMappingCSI-RS-ResourceMapping, powerControlOffset INTEGER (−8..15),powerControlOffsetSS ENUMERATED{db−3, db0, db3, db6} OPTIONAL, -- Need RscramblingID ScramblingId, periodicityAndOffsetCSI-ResourcePeriodicityAndOffset OPTIONAL, -- CondPeriodicOrSemiPersistent qcl-InfoPeriodicCSI-RS TCI-StateId OPTIONAL, --Cond Periodic ... } -- TAG-NZP-CSI-RS-RESOURCE-STOP -- ASN1STOP

TABLE 13 NZP-CSI-RS-Resource field descriptions periodicityAndOffsetPeriodicity and slot offset sl1 corresponds to a periodicity of 1 slot,sl2 to a periodicity of two slots, and so on. The corresponding offsetis also given in number of slots. powerControlOffset Power offset ofPDSCH RE to NZP CSI-RS RE. Value in dB. powerControlOffsetSS Poweroffset of NZP CSI-RS RE to SS RE. Value in dB. qcl-InfoPeriodicCSI-RSFor a target periodic CSI-RS, contains a reference to one TCI-State inTCI-States for providing the QCL source and QCL type. For periodicCSI-RS, the source can be SSB or another periodic-CSI-RS. Refers to theTCI-State which has this value for tci-StateId and is defined intci-StatesToAddModList in the PDSCH-Config included in the BWP-Downlinkcorresponding to the serving cell and to the DL BWP to which theresource belongs to. resourceMapping OFDM symbol location(s) in a slotand subcarrier occupancy in a PRB of the CSI-RS resource scramblingIDScrambling ID

In the example of table 13, the periodic field is optionally present,need M, for periodic NZP CSI-RS resources (as indicated inCSI-ResourceConfig); otherwise, the field is absent. In the example oftable 13, the PeriodicOrSemiPersistent field is mandatory present, needM, for periodic and semi-persistent NZP CSI-RS resources (as indicatedin CSI-ResourceConfig); otherwise, the field is absent. Additionally,example NZP-CSI-RS-ResourceId IE and NZP-CSI-RS-ResourceSetId IE areshown by tables 14 and 15, respectively.

TABLE 14 NZP-CSI-RS-ResourceId information element -- ASN1START --TAG-NZP-CSI-RS-RESOURCEID-START NZP-CSI-RS-ResourceId ::= INTEGER(0..maxNrofNZP-CSI-RS-Resources−1) -- TAG-NZP-CSI-RS-RESOURCEID-STOP --ASN1STOP

TABLE 15 NZP-CSI-RS-ResourceSetId information element -- ASN1START --TAG-NZP-CSI-RS-RESOURCESETID-START NZP-CSI-RS-ResourceSetId ::= INTEGER(0..maxNrofNZP-CSI-RS-ResourceSets−1) --TAG-NZP-CSI-RS-RESOURCESETID-STOP -- ASN1STOP

If a UE is configured with a NZP-CSI-RS-ResourceSet configured with thehigher layer parameter repetition set to ‘on’, the UE may assume thatthe CSI-RS resources within the NZP-CSI-RS-ResourceSet are transmittedwith the same downlink spatial domain transmission filter, where theCSI-RS resources in the NZP-CSI-RS-ResourceSet are transmitted indifferent OFDM symbols. If repetition is set to ‘off’, the UE shall notassume that the CSI-RS resources within the NZP-CSI-RS-ResourceSet aretransmitted with the same downlink spatial domain transmission filter.

Furthermore, the NZP-CSI-RS-Resource IE includes aqcl-InfoPeriodicCSI-RS field, which contains a reference to a TCI-Statein a TCI-State IE for providing a QCL source and QCL type for a targetperiodic CSI-RS. The TCI-State IE associates one or two DL referencesignals with a corresponding QCL type. The TCI-State IE includes aTCI-StateId, which is used to identify one TCI-State configuration. Anexample TCI-State IE is shown by table 16a, an example TCI-StateId IE isshown by table 16b, and field descriptions for the TCI-State IE areshown by table 17.

TABLE 16a TCI-State information element -- ASN1START --TAG-TCI-STATE-START TCI-State ::= SEQUENCE { tci-StateId TCI-StateId,qcl-Type1 QCL-Info, qcl-Type2 QCL-Info OPTIONAL, -- Need R ... }QCL-Info ::= SEQUENCE { cell ServCellIndex OPTIONAL, -- Need R bwp-IdBWP-Id OPTIONAL, -- Cond CSI-RS-Indicated referenceSignal CHOICE {csi-rs NZP-CSI-RS-ResourceId, ssb SSB-Index }, qcl-Type ENUMERATED{typeA, typeB, typeC, typeD}, ... } -- TAG-TCI-STATE-STOP -- ASN1STOP

TABLE 16b TCI-StateId information element -- ASN1START --TAG-TCI-STATEID-START TCI-StateId ::= INTEGER (0..maxNrofTCI-States−1)-- TAG-TCI-STATEID-STOP -- ASN1STOP

TABLE 17 TCI-State field descriptions QCL-Info field descriptions bwp-IdThe DL BWP which the RS is located in. cell The UE's serving cell inwhich the referenceSignal is configured. If the field is absent, itapplies to the serving cell in which the TCI-State is configured. The RScan be located on a serving cell other than the serving cell in whichthe TCI-State is configured only if the qcl-Type is configured as typeCor typeD. referenceSignal Reference signal with which quasi-collocationinformation is discussed elsewhere qcl-Type QCL type.

In embodiments, the TCI-State IE may be included in atci-StatesPDCCH-ToAddList IE of a ControlResourceSet IE or aPDSCH-Config IE. In these embodiments, the tci-StatesPDCCH-ToAddList IEincludes a list of Transmission Configuration Indicator (TCI) statesindicating a transmission configuration which includes QCL-relationshipsbetween the DL RSs in one RS set and the PDSCH DMRS ports. ThePDSCH-Config IE is used to configure the UE specific PDSCH parameters.The ControlResourceSet IE is used to configure a time/frequency controlresource set (CORESET) in which to search for downlink controlinformation.

In some embodiments, the TCI-State IE may be included in a qcl-info IEof a CSI-AperiodicTriggerStateList IE. The CSI-AperiodicTriggerStateListIE is used to configure the UE 101 with a list of aperiodic triggerstates. Each codepoint of the DCI field “CSI request” is associated withone trigger state. Upon reception of the value associated with a triggerstate, the UE will perform measurement of CSI-RS (reference signals) andaperiodic reporting on L1 according to all entries in theassociatedReportConfigInfoList for that trigger state. The qcl-info IEin the CSI-AperiodicTriggerStateList IE includes a list of references toTCI-States for providing the QCL source and QCL type for eachNZP-CSI-RS-Resource listed in nzp-CSI-RS-Resources of theNZP-CSI-RS-ResourceSet indicated by nzp-CSI-RS-ResourcesforChannel. EachTCI-StateId refers to the TCI-State which has this value for tci-StateIdand is defined in tci-StatesToAddModList in the PDSCH-Config included inthe BWP Downlink corresponding to the serving cell and to the DL BWP towhich the resourcesForChannelMeasurement (in the CSI-ReportConfigindicated by reportConfigId) belong. A first entry inqcl-info-forChannel corresponds to a first entry in nzp-CSI-RS-Resourcesof that NZP-CSI-RS-ResourceSet IE, a second entry in qcl-info-forChannelcorresponds to a second entry in the nzp-CSI-RS-Resources, and so forth.

In addition to the aforementioned examples, the RRC message may alsoinclude an SRS configuration (SRS-Config) IE, which is used to configuresounding reference signal transmissions. The SRS-Config defines a listof SRS resources (SRS-Resources) and a list of SRS resource sets(SRS-ResourceSets). Each resource set defines a set of SRS-Resources. Inembodiments, the network (e.g., a RAN node 111) triggers thetransmission of the set of SRS-Resources using a configuredaperiodicSRS-ResourceTrigger (L1 DCI). An example SRS-Config IE is shownby table 18, and field descriptions for the SRS-Config are shown bytable 19.

TABLE 18 SRS-Config information element -- ASN1START --TAG-SRS-CONFIG-START SRS-Config ::= SEQUENCE {srs-ResourceSetToReleaseList SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSetId OPTIONAL, -- Need Nsrs-ResourceSetToAddModList SEQUENCE (SIZE(1..maxNrofSRS- ResourceSets))OF SRS-ResourceSet OPTIONAL, -- Need N srs-ResourceToReleaseListSEQUENCE (SIZE(1..maxNrofSRS-Resources)) OF SRS-ResourceId OPTIONAL, --Need N srs-ResourceToAddModList SEQUENCE (SIZE(1..maxNrofSRS-Resources)) OF SRS-Resource OPTIONAL, -- Need Ntpc-Accumulation ENUMERATED (disabled) OPTIONAL, -- Need S ... }SRS-ResourceSet ::= SEQUENCE { srs-ResourceSetId SRS-ResourceSetId,srs-ResourceIdList SEQUENCE (SIZE(1..maxNrofSRS- ResourcesPerSet)) OFSRS-ResourceId OPTIONAL, -- Cond Setup resourceType CHOICE { aperiodicSEQUENCE { aperiodicSRS-ResourceTrigger INTEGER (1..maxNrofSRS-TriggerStates-1), csi-RS NZP-CSI-RS-ResourceId OPTIONAL, -- CondNonCodebook slotOffset INTEGER (1..32) OPTIONAL, -- Need S ..., [[aperiodicSRS-ResourceTriggerList-v1530 SEQUENCE(SIZE(1..maxNrofSRS-TriggerStates−2)) OF INTEGER(1..maxNrofSRS-TriggerStates−1)  OPTIONAL -- Need M ]] },semi-persistent SEQUENCE { associatedCSI-RS NZP-CSI-RS-ResourceIdOPTIONAL, -- Cond NonCodebook ... }, periodic SEQUENCE {associatedCSI-RS NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebook ...} }, usage ENUMERATED (beamManagement, codebook, nonCodebook,antennaSwitching), alpha Alpha OPTIONAL, -- Need S p0 INTEGER (−202..24)OPTIONAL, -- Cond Setup pathlossReferenceRS CHOICE { ssb-IndexSSB-Index, csi-RS-Index NZP-CSI-RS-ResourceId } OPTIONAL, -- Need Msrs-PowerControlAdjustmentStates ENUMERATED { sameAsFci2,separateClosedLoop}  OPTIONAL, -- Need S ... } SRS-ResourceSetId ::=INTEGER (0..maxNrofSRS-ResourceSets−1) SRS-Resource ::= SEQUENCE {srs-ResourceId SRS-ResourceId, nrofSRS-Ports ENUMERATED {port1, ports2,ports4}, ptrs-PortIndex ENUMERATED {n0, n1 } OPTIONAL, -- Need RtransmissionComb CHOICE { n2 SEQUENCE { combOffset-n2 INTEGER (0..1),cyclicShift-n2 INTEGER (0..7) }, n4 SEQUENCE { combOffset-n4 INTEGER(0..3), cyclicShift-n4 INTEGER (0..11) } }, resourceMapping SEQUENCE {startPosition INTEGER (0..5), nrofSymbols ENUMERATED {n1, n2, n4},repetitionFactor ENUMERATED {n1, n2, n4} }, freqDomainPosition INTEGER(0..67), freqDomainShift INTEGER (0..268), freqHopping SEQUENCE { c-SRSINTEGER (0..63), b-SRS INTEGER (0..3), b-hop INTEGER (0..3) },groupOrSequenceHopping ENUMERATED { neither, groupHopping,sequenceHopping }, resourceType CHOICE { aperiodic SEQUENCE { ... },semi-persistent SEQUENCE { periodicityAndOffset-spSRS-PeriodicityAndOffset, ... }, periodic SEQUENCE {periodicityAndOffset-p SRS-PeriodicityAndOffset, ... } }, sequenceIdINTEGER (0..1023), spatialRelationInfo SRS-SpatialRelationInfo OPTIONAL,-- Need R ... } SRS-SpatialRelationInfo ::= SEQUENCE { servingCellIdServCellIndex OPTIONAL, -- Need S referenceSignal CHOICE { ssb-IndexSSB-Index, csi-RS-Index NZP-CSI-RS-ResourceId, srs SEQUENCE { resourceIdSRS-ResourceId, uplinkBWP BWP-Id } } } SRS-ResourceId ::= INTEGER(0..maxNrofSRS-Resources−1) SRS-PeriodicityAndOffset ::= CHOICE { sl1NULL, sl2 INTEGER(0..1), sl4 INTEGER(0..3), sl5 INTEGER(0..4), sl8INTEGER(0..7), sl10 INTEGER(0..9), sl16 INTEGER(0..15), sl20INTEGER(0..19), sl32 INTEGER(0..31), sl40 INTEGER(0..39), sl64INTEGER(0..63), sl80 INTEGER(0..79), sl160 INTEGER(0..159), sl320INTEGER(0..319), sl640 INTEGER(0..639), sl1280 INTEGER(0..1279), sl2560INTEGER(0..2559) } -- TAG-SRS-CONFIG-STOP -- ASN1STOP

TABLE 19 SRS-Config field descriptions SRS-Resource field descriptionstpc-Accumulation If the field is absent, UE applies TPC commands viaaccumulation. If disabled, UE applies the TPC command withoutaccumulation (this applies to SRS when a separate closed loop isconfigured for SRS). SRS-Resource field descriptions cyclicShift-n2Cyclic shift configuration cyclicShift-n4 Cyclic shift configurationfreqHopping Includes parameters capturing SRS frequency hoppinggroupOrSequenceHopping Parameter(s) for configuring group or sequencehopping periodicityAndOffset-p Periodicity and slot offset for this SRSresource. All values in “number of slots” sl1 corresponds to aperiodicity of 1 slot, value sl2 corresponds to a periodicity of 2slots, and so on. For each periodicity the corresponding offset is givenin number of slots. For periodicity sl1 the offset is 0 slotsperiodicityAndOffset-sp Periodicity and slot offset for this SRSresource. All values in “number of slots”. sl1 corresponds to aperiodicity of 1 slot, value sl2 corresponds to a periodicity of 2slots, and so on. For each periodicity the corresponding offset is givenin number of slots. For periodicity sl1 the offset is 0 slotsptrs-PortIndex The PTRS port index for this SRS resource fornon-codebook based UL MIMO. This is only applicable when thecorresponding PTRS-UplinkConfig is set to CP-OFDM. The ptrs-PortIndexconfigured here must be smaller than or equal to the maxNnrofPortsconfigured in the PTRS-UplinkConfig resourceMapping OFDM symbol locationof the SRS resource within a slot including number of OFDM symbols (N =1, 2 or 4 per SRS resource), startPosition (SRSSymbolStartPosition = 0 .. . 5; “0” refers to the last symbol, “1” refers to the second lastsymbol) and RepetitionFactor (r = 1, 2 or 4). The configured SRSresource does not exceed the slot boundary. resource Type Periodicityand offset for semi-persistent and periodic SRS resource sequenceIdSequence ID used to initialize pseudo random group and sequence hoppingspatialRelationInfo Configuration of the spatial relation between areference RS and the target SRS. Reference RS can be SSB/CSI-RS/SRStransmissionComb Comb value (2 or 4) and comb offset (0 . . . combValue− 1) SRS-ResourceSet field descriptions alpha alpha value for SRS powercontrol. When the field is absent the UE applies the value 1.aperiodicSRS-ResourceTriggerList An additional list of DCI “code points”upon which the UE shall transmit SRS according to this SRS resource setconfiguration. aperiodicSRS-ResourceTrigger The DCI “code point” uponwhich the UE shall transmit SRS according to this SRS resource setconfiguration. associatedCSI-RS ID of CSI-RS resource associated withthis SRS resource set in non-codebook based operation. csi-RS ID ofCSI-RS resource associated with this SRS resource set. p0 P0 value forSRS power control. The value is in dBm. Only even values (step size 2)are allowed. pathlossReferenceRS A reference signal (e.g. a CSI-RSconfig or a SS block) to be used for SRS path loss estimation.resourceType Time domain behavior of SRS resource configuration.Corresponds to L1 parameter ‘SRS- ResourceConfigType’. The networkconfigures SRS resources in the same resource set with the same timedomain behavior on periodic, aperiodic and semi-persistent SRS.slotOffset An offset in number of slots between the triggering DCI andthe actual transmission of this SRS- ResourceSet. If the field is absentthe UE applies no offset (value 0). srs-PowerControlAdjustmentStatesIndicates whether hsrs, c(i) = fc(i, 1) or hsrs, c(i) = fc(i, 2) (iftwoPUSCH-PC-AdjustmentStates are configured) or serarate close loop isconfigured for SRS. This parameter is applicable only for UIs on whichUE also transmits PUSCH. If absent or release, the UE applies the valuesameAs-Fci1. srs-ResourceIdList The IDs of the SRS-Resources used inthis SRS-ResourceSet. If this SRS-ResourceSet is configured with usageset to codebook, the srs-ResourceIdList contains at most 2 entries. Ifthis SRS- ResourceSet is configured with usage set to nonCodebook, thesrs-ResourceIdList contains at most 4 entries. srs-ResourceSetId The IDof this resource set. It is unique in the context of the BWP in whichthe parent SRS-Config is defined. usage Indicates if the SRS resourceset is used for beam management, codebook based or non-codebook basedtransmission or antenna switching.

As shown by the examples of tables 18 and 19, the SRS-Config IE includesone or more SRS-ResourceSet IE, which may include one or moreSRS-Resource IEs. Each SRS-Resource IE may include a resource Typeparameter and a spatialRelationInfo parameter with anSRS-SpatialRelationInfo value, which indicates or is a configuration ofthe spatial relation between a reference RS and a target SRS. The UE 101can be configured with one or more SRS resource sets via theSRS-ResourceSet IE. For codebook based transmission, the UE 101 may beconfigured with a single SRS-ResourceSet set to ‘codebook’ and only oneSRS resource can be indicated based on the SRI from within the SRSresource set. The SRS-ResourceSet IE is also used to configureAperiodicSRS-ResourceTrigger (indicating the association betweenaperiodic SRS triggering state and SRS resource sets), triggered SRSresource(s) srs-ResourceSetId, csi-RS (indicating the associatedNZP-CSI-RS-ResourceId) for an SRS-Resource IE with a resourceTypeparameter configured with a value of “aperiodic.” The UE 101 receives aconfiguration of SRS resource sets when the UE 101 is configured withone or more SRS resource configuration(s), and when the higher layerparameter resourceType in the SRS-Resource IE is set to ‘aperiodic’.

In various embodiments, for uplink codebook based transmissions, if theSRS-Resource IE has a resourceType parameter configured with a value“semi-persistent,” the UE 101 expects the SRS resource(s) indicated bythe SRS-Resource IE to be activated (e.g., by a suitable DCI) and uses asame spatial domain filter to transmit a PUSCH as an activated SRSresource for codebook based transmission. If such SRS resource(s) arenot activated (e.g., by a suitable DCI), the UE 101 applies the samespatial domain filter to transmit the PUSCH as the parameterSRS-SpatialRelationInfo configured for the indicated SRS. Additionallyor alternatively, the PUSCH beam may be the same as the beam used for aparticular PUCCH resource or a particular SRS resource for beammanagement.

The NAS 1157 may form the highest stratum of the control plane betweenthe UE 101 and the AMF 621. The NAS 1157 may support the mobility of theUEs 101 and the session management procedures to establish and maintainIP connectivity between the UE 101 and a P-GW in LTE systems.

According to various embodiments, one or more protocol entities ofarrangement 1100 may be implemented in UEs 101, RAN nodes 111, AMF 621in NR implementations or 1\.1 MME 521 in LTE implementations, UPF 602 inNR implementations or S-GW 522 and P-GW 523 in LTE implementations, orthe like to be used for control plane or user plane communicationsprotocol stack between the aforementioned devices. In such embodiments,one or more protocol entities that may be implemented in one or more ofUE 101, gNB 111, A1\.1F 621, etc. may communicate with a respective peerprotocol entity that may be implemented in or on another device usingthe services of respective lower layer protocol entities to perform suchcommunication. In some embodiments, a gNB-CU of the gNB 111 may host theRRC 1155, SDAP 1147, and PDCP 1140 of the gNB that controls theoperation of one or more gNB-DUs, and the gNB-DUs of the gNB 111 mayeach host the RLC 1130, MAC 1120, and PHY 1110 of the gNB 111.

In a first example, a control plane protocol stack may comprise, inorder from highest layer to lowest layer, NAS 1157, RRC 1155, PDCP 1140,RLC 1130, MAC 1120, and PHY 1110. In this example, upper layers 1160 maybe built on top of the NAS 857, which includes an IP layer 1161, an SCTP1162, and an application layer signaling protocol (AP) 1163.

In NR implementations, the AP 1163 may be an NG application protocollayer (NGAP or NG-AP) 1163 for the NG interface 113 defined between theNG-RAN node 111 and the AMF 621, or the AP 1163 may be an Xn applicationprotocol layer (XnAP or Xn-AP) 1163 for the Xn interface 112 that isdefined between two or more RAN nodes 111.

The NG-AP 1163 may support the functions of the NG interface 113 and maycomprise Elementary Procedures (EPs). An NG-AP EP may be a unit ofinteraction between the NG-RAN node 111 and the AMF 621. The NG-AP 1163services may comprise two groups: UE-associated services (e.g., servicesrelated to a UE 101) and non-UE-associated services (e.g., servicesrelated to the whole NG interface instance between the NG-RAN node 111and AMF 621). These services may include functions including, but notlimited to: a paging function for the sending of paging requests toNG-RAN nodes 111 involved in a particular paging area; a UE contextmanagement function for allowing the AMF 621 to establish, modify,and/or release a UE context in the AMF 621 and the NG-RAN node 111; amobility function for UEs 101 in ECM-CONNECTED mode for intra-system HOsto support mobility within NG-RAN and inter-system HOs to supportmobility from/to EPS systems; a NAS Signaling Transport function fortransporting or rerouting NAS messages between UE 101 and AMF 621; a NASnode selection function for determining an association between the AMF621 and the UE 101; NG interface management function(s) for setting upthe NG interface and monitoring for errors over the NG interface; awarning message transmission function for providing means to transferwarning messages via NG interface or cancel ongoing broadcast of warningmessages; a Configuration Transfer function for requesting andtransferring of RAN configuration information (e.g., SON information,performance measurement (PM) data, etc.) between two RAN nodes 111 viaCN 120; and/or other like functions.

The XnAP 1163 may support the functions of the Xn interface 112 and maycomprise XnAP basic mobility procedures and XnAP global procedures. TheXnAP basic mobility procedures may comprise procedures used to handle UEmobility within the NG RAN 111 (or E-UTRAN 510), such as handoverpreparation and cancellation procedures, SN Status Transfer procedures,UE context retrieval and UE context release procedures, RAN pagingprocedures, dual connectivity related procedures, and the like. The XnAPglobal procedures may comprise procedures that are not related to aspecific UE 101, such as Xn interface setup and reset procedures, NG-RANupdate procedures, cell activation procedures, and the like.

In LTE implementations, the AP 1163 may be an S1 Application Protocollayer (S1-AP) 1163 for the S1 interface 113 defined between an E-UTRANnode 111 and an MME, or the AP 1163 may be an X2 application protocollayer (X2AP or X2-AP) 1163 for the X2 interface 112 that is definedbetween two or more E-UTRAN nodes 111.

The S1 Application Protocol layer (S1-AP) 1163 may support the functionsof the S1 interface, and similar to the NG-AP discussed previously, theS1-AP may comprise S1-AP EPs. An S1-AP EP may be a unit of interactionbetween the E-UTRAN node 111 and an MME 521 within an LTE CN 120. TheS1-AP 1163 services may comprise two groups: UE-associated services andnon UE-associated services. These services perform functions including,but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UEcapability indication, mobility, NAS signaling transport, RANInformation Management (RIM), and configuration transfer.

The X2AP 1163 may support the functions of the X2 interface 112 and maycomprise X2AP basic mobility procedures and X2AP global procedures. TheX2AP basic mobility procedures may comprise procedures used to handle UEmobility within the E-UTRAN 120, such as handover preparation andcancellation procedures, SN Status Transfer procedures, UE contextretrieval and UE context release procedures, RAN paging procedures, dualconnectivity related procedures, and the like. The X2AP globalprocedures may comprise procedures that are not related to a specific UE101, such as X2 interface setup and reset procedures, load indicationprocedures, error indication procedures, cell activation procedures, andthe like.

The SCTP layer (alternatively referred to as the SCTP/IP layer) 1162 mayprovide guaranteed delivery of application layer messages (e.g., NGAP orXnAP messages in NR implementations, or S1-AP or X2AP messages in LTEimplementations). The SCTP 1162 may ensure reliable delivery ofsignaling messages between the RAN node 111 and the AMF 621/MME 521based, in part, on the IP protocol, supported by the IP 1161. TheInternet Protocol layer (IP) 1161 may be used to perform packetaddressing and routing functionality. In some implementations the IPlayer 1161 may use point-to-point transmission to deliver and conveyPDUs. In this regard, the RAN node 111 may comprise L2 and L1 layercommunication links (e.g., wired or wireless) with the MME/AMF toexchange information.

In a second example, a user plane protocol stack may comprise, in orderfrom highest layer to lowest layer, SDAP 1147, PDCP 1140, RLC 1130, MAC820, and PHY 810. The user plane protocol stack may be used forcommunication between the UE 101, the RAN node 111, and UPF 602 in NRimplementations or an S-GW 522 and P-GW 523 in LTE implementations. Inthis example, upper layers 1151 may be built on top of the SDAP 1147,and may include a user datagram protocol (UDP) and IP security layer(UDP/IP) 1152, a General Packet Radio Service (GPRS) Tunneling Protocolfor the user plane layer (GTP-U) 1153, and a User Plane PDU layer (UPPDU) 1163.

The transport network layer 1154 (also referred to as a “transportlayer”) may be built on IP transport, and the GTP-U 1153 may be used ontop of the UDP/IP layer 1152 (comprising a UDP layer and IP layer) tocarry user plane PDUs (UP-PDUs). The IP layer (also referred to as the“Internet layer”) may be used to perform packet addressing and routingfunctionality. The IP layer may assign IP addresses to user data packetsin any of IPv4, IPv6, or PPP formats, for example.

The GTP-U 1153 may be used for carrying user data within the GPRS corenetwork and between the radio access network and the core network. Theuser data transported can be packets in any of IPv4, IPv6, or PPPformats, for example. The UDP/IP 1152 may provide checksums for dataintegrity, port numbers for addressing different functions at the sourceand destination, and encryption and authentication on the selected dataflows. The RAN node 111 and the S-GW 522 may utilize an S1-U interfaceto exchange user plane data via a protocol stack comprising an L1 layer(e.g., PHY 1110), an L2 layer (e.g., MAC 1120, RLC 1130, PDCP 1140,and/or SDAP 1147), the UDP/IP layer 1152, and the GTP-U 1153. The S-GW522 and the P-GW 523 may utilize an S5/S8a interface to exchange userplane data via a protocol stack comprising an L1 layer, an L2 layer, theUDP/IP layer 1152, and the GTP-U 1153. As discussed previously, NASprotocols may support the mobility of the UE 101 and the sessionmanagement procedures to establish and maintain IP connectivity betweenthe UE 101 and the P-GW 523.

Moreover, although not shown by FIG. 11, an application layer may bepresent above the AP 1163 and/or the transport network layer 1154. Theapplication layer may be a layer in which a user of the UE 101, RAN node111, or other network element interacts with software applications beingexecuted, for example, by application circuitry 705 or applicationcircuitry 805, respectively. The application layer may also provide oneor more interfaces for software applications to interact withcommunications systems of the UE 101 or RAN node 111, such as thebaseband circuitry 1010. In some implementations the IP layer and/or theapplication layer may provide the same or similar functionality aslayers 5-7, or portions thereof, of the Open Systems Interconnection(OSI) model (e.g., OSI Layer 7—the application layer, OSI Layer 6—thepresentation layer, and OSI Layer 5—the session layer).

FIGS. 12-14 show example procedures 1200-1400, respectively, inaccordance with various embodiments. For illustrative purposes, thevarious operations of processes 900-1100 is described as being performedby UEs 101 of FIG. 1 or elements thereof (e.g., components discussedwith regard to platform 800 of FIG. 8), or a RAN node 111 of FIG. 1 orelements thereof (e.g., components discussed with regard toinfrastructure equipment 700 of FIG. 7). Additionally, the variousmessages/signaling communicated between the UE 101 and RAN node 111 maybe sent/received over the various interfaces discussed herein withrespect to FIGS. 1-11, and using the various mechanisms discussed hereinincluding those discussed herein with respect to FIGS. 1-11. Whileparticular examples and orders of operations are illustrated FIGS.12-14, the depicted orders of operations should not be construed tolimit the scope of the embodiments in any way. Rather, the depictedoperations may be re-ordered, broken into additional operations,combined, and/or omitted altogether while remaining within the spiritand scope of the present disclosure.

FIG. 12 depicts an example UL MIMO procedure 1200 according to variousembodiments. Process 1200 may be performed by the UE 101. Process 1200begins at operation 1205 where the UE 101 determines whether an SRS (orSRS resource) is configured for a current transmission scheme. Thetransmission scheme may be a codebook based transmission scheme or anon-codebook based transmission scheme. The UE 101 may determine whetheran SRS (or SRS resource) is configured by searching for or otherwiseidentifying an SRS-Resource IE in an SRS-ResourceSet IE of an SRSconfiguration (SRS-Config) in an RRC message, such as those discussedpreviously.

If at operation 1205 the UE 101 determines that the configuration doesinclude a configured SRS, then the UE 101 proceeds to operation 1210 tofollow the transmission scheme and indicated SRI for a PUSCHtransmission. In an example for uplink codebook based transmissions, ifthe SRS-Resource IE has a resource Type parameter configured with avalue “semi-persistent,” the UE 101 expects the SRS resource(s)indicated by the SRS-Resource IE to be activated (e.g., by a suitableDCI) and uses a same spatial domain filter to transmit a PUSCH as anactivated SRS resource for codebook based transmission. The process 1200ends after performance of operation 1210.

If at operation 1205 the UE 101 determines that the configuration doesnot include a configured SRS, then the UE 101 proceeds to operation 1215to perform the a fallback procedure, which is triggered by a fallbackDCI such as a DCI format 0_0. The UE 101 then proceeds to operation 1225transmit the PUSCH. In an example for uplink codebook basedtransmissions, if the SRS-Resource IE has a resource Type parameterconfigured with a value “semi-persistent,” and the SRS resource(s)indicated by the SRS-Resource IE are not activated (e.g., by a suitableDCI), then the UE 101 at operation 1225 applies the same spatial domainfilter to transmit the PUSCH as the parameter SRS-SpatialRelationInfoconfigured for the indicated SRS. Additionally or alternatively, thePUSCH beam may be the same as the beam used for a particular PUCCHresource or a particular SRS resource for beam management. The process1200 ends after performance of operation 1225.

FIG. 13 shows an example configuration process 1300 according to variousembodiments. Process 1300 begins at operation 1305 where the UE 101determines an SRS and/or CSI-RS configurations, such as by searching orotherwise identifying an SRS-Config and/or an NZP-CSI-RS-ResourceSet IEsas discussed previously. At operation 1310 to identify one of a trs-Infoparameter or a Repetition parameter set to “ON.” In embodiments, onlyone of the trs-Info or the repetition parameter can be set to ‘ON’ inthe NZP-CSI-RS-ResourceSet, or only one of the trs-Info parameter or therepetition parameter can be configured in the NZP-CSI-RS-ResourceSet.After operation 1310, process 1300 ends or repeats as necessary.

FIG. 14 depicts an example process 1400 according to variousembodiments. Process 1400 may be performed by the UE 101. Process 1400begins at operation 1405 where the UE 101 receives an RRC message, whichmay include an SRS configuration as discussed previously. Sometime laterat operation 1410, the UE 101 receives a DCI, for example, in a PDCCH.At operation 1415, the UE 101 determines whether the DCI indicates anSRS resource indicated by an SRS configuration in the RRC message.

If at operation 1410 the UE 101 determines that at least one SRSresource is configured for a configured transmission scheme (e.g.,codebook or non-codebook based transmission scheme) via the RRC messagereceived at operation 1405 and the at least one configured SRS resourceis indicated by the DCI received at operation 1410, the UE 101 proceedsto operation 1420 to transmit an SRS in the at least one configured SRSresource. Process 1400 ends after performance of operation 1420.

If at operation 1410 the UE 101 determines that the at least oneconfigured SRS resource is not indicated by the DCI received atoperation 1410, regardless of whether that at least one SRS resource isconfigured for a configured transmission scheme (e.g., codebook ornon-codebook based transmission scheme) via the RRC message received atoperation 1405, the UE 101 proceeds to operation 1425 to transmit aPUSCH scheduled by the DCI in a corresponding PUCCH resource with alowest resource ID within an active UL BWP. Process 1400 ends afterperformance of operation 1425.

Some non-limiting examples are as follows. The following examplespertain to further embodiments, and specifics in the examples may beused anywhere in one or more embodiments discussed previously. Any ofthe following examples may be combined with any other example or anyembodiment discussed herein.

Examples 1 includes one or more computer-readable storage media (CRSM)comprising instructions, wherein execution of the instructions by one ormore processors of a user equipment (UE) is to cause the UE to: when theUE is configured with at least one sounding reference signal (SRS)resource for a configured transmission scheme via a higher layerparameter and the at least one configured SRS resource is indicated by areceived downlink control information (DCI) or Radio Resource Control(RRC) message, control transmission of an SRS in the at least oneconfigured SRS resource; and when the UE is not configured with at leastone SRS resource, control transmission of a physical uplink sharedchannel (PUSCH) scheduled by a DCI in a corresponding physical uplinkcontrol channel (PUCCH) resource with a lowest resource identifier (ID)within an active uplink (UL) bandwidth part (BWP).

Examples 2 includes the one or more CRSM of example 1 and/or some otherexamples herein, wherein the PUSCH is a codebook based transmission or anon-codebook based transmission.

Examples 3 includes the one or more CRSM of examples 1-2 and/or someother examples herein, wherein a DCI format of the received DCI is DCIformat 0_0 when the UE is not configured with at least one SRS resource,and the DCI format of the received DCI is DCI format 0_1 or DCI format1_1 when the UE is configured with at least one SRS resource.

Examples 4 includes the one or more CRSM of example 3 and/or some otherexamples herein, when the DCI is the DCI format 0_0, execution of theinstructions is to cause the UE to: control transmission of the PUSCH inthe corresponding PUCCH resource with the lowest resource ID within theactive UL BWP.

Examples 5 includes the one or more CRSM of examples 1-4 and/or someother examples herein, wherein execution of the instructions is to causethe UE to: control receipt of a radio resource control (RRC) message,the RRC message to include an SRS configuration (SRS-Config), theSRS-Config to include one or more sounding reference signal resourcesets (SRS-ResourceSets), each SRS-ResourceSet of the one or moreSRS-ResourceSets to indicate one or more SRS resources, and the one ormore SRS resources of each SRS-ResourceSet are configured to be used forone of periodic SRS transmissions, semi-persistent SRS transmissions, oraperiodic SRS transmissions.

Examples 6 includes the one or more CRSM of example 5 and/or some otherexamples herein, wherein at least one SRS-ResourceSet of the one or moreSRS-ResourceSets includes the at least one configured SRS resource.

Examples 7 includes the one or more CRSM of example 6 and/or some otherexamples herein, wherein the at least one configured SRS resource isconfigured to be used for aperiodic SRS transmissions, and the receivedDCI includes an SRS request field indicating the at least one configuredSRS resource to trigger transmission of the aperiodic SRS, wherein onlyone SRS resource within the SRS-ResourceSet configuration can betriggered.

Examples 8 includes the one or more CRSM of examples 5-7 and/or someother examples herein, wherein at least one SRS-ResourceSet of the oneor more SRS-ResourceSets includes one or more SRS resources configuredto be used for semi-persistent SRS transmissions, and execution of theinstructions is to cause the UE to: use a same spatial domain filter totransmit the PUSCH as the at least one configured SRS resource indicatedby the received DCI when the at least one configured SRS resourceindicated by the received DCI is among the one or more SRS resourcesconfigured to be used for semi-persistent SRS transmissions.

Examples 9 includes the one or more CRSM of examples 5-8 and/or someother examples herein, wherein the SRS-Config is to include a spatialrelation (spatialRelationInfo) configuration to indicate a spatialrelation between a reference RS and a target SRS, at least oneSRS-ResourceSet of the one or more SRS-ResourceSets includes one or moreSRS resources configured to be used for semi-persistent SRStransmissions, and execution of the instructions is to cause the UE to:use a same spatial domain filter to transmit the PUSCH as the at leastone configured SRS resource indicated by the spatialRelationInfoconfiguration when the at least one configured SRS resource is among theone or more SRS resources configured to be used for semi-persistent SRStransmissions, and the at least one configured SRS resource is notindicated by the received DCI.

Examples 10 includes the one or more CRSM of examples 5-9 and/or someother examples herein, wherein the RRC message is to include a non-zeropower channel state information reference signal resource set(NZP-CSI-RS-ResourceSet), and the NZP-CSI-RS-ResourceSet is to indicateone or more non-zero power channel state information reference signal(NZP CSI-RS) resources, and execution of the instructions is to causethe UE to: assume same antenna ports are to be used for the NZP CSI-RSresources in the NZP-CSI-RS-ResourceSet having a same port index whenthe NZP-CSI-RS-ResourceSet includes a trs-Info parameter set to ‘on’;and assume that the NZP CSI-RS resources in the NZP-CSI-RS-ResourceSetare to be transmitted with a same downlink spatial domain transmissionfilter when the NZP-CSI-RS-ResourceSet includes a repetition parameterset to ‘on’, wherein only one of the trs-Info or the repetition can beconfigured by the NZP-CSI-RS-ResourceSet.

Examples 11 includes the one or more CRSM of example 10 and/or someother examples herein, wherein the NZP-CSI-RS-ResourceSet is to includea QCL-Info-PeriodicCSI-RS parameter to indicate a transmission beam forindividual ones of the one or more NZP CSI-RS resources.

Examples 12 includes a System-on-Chip (SoC) to be implemented in a userequipment (UE), the SoC comprising: interface circuitry arranged toobtain a radio resource control (RRC) message that includes a non-zeropower channel state information reference signal resource set(NZP-CSI-RS-ResourceSet), the NZP-CSI-RS-ResourceSet to indicate one ormore non-zero power channel state information reference signal (NZPCSI-RS) resources; and baseband circuitry coupled with the interfacecircuitry, the baseband circuitry arranged to: assume same antenna portsare to be used for the NZP CSI-RS resources in theNZP-CSI-RS-ResourceSet having a same port index when theNZP-CSI-RS-ResourceSet includes a trs-Info parameter set to ‘on’; andassume that the NZP CSI-RS resources in the NZP-CSI-RS-ResourceSet areto be transmitted with a same downlink spatial domain transmissionfilter when the NZP-CSI-RS-ResourceSet includes a repetition parameterset to ‘on’, wherein only one of the trs-Info or the repetition can beconfigured by the NZP-CSI-RS-ResourceSet.

Examples 13 includes the SoC of example 12 and/or some other examplesherein, wherein the NZP-CSI-RS-ResourceSet is to include aQCL-Info-PeriodicCSI-RS parameter to indicate a transmission beam forindividual ones of the one or more NZP CSI-RS resources.

Examples 14 includes the SoC of examples 12-13 and/or some otherexamples herein, wherein the baseband circuitry is arranged to: controltransmission of a sounding reference signal (SRS) in at least oneconfigured SRS resource when the at least one configured SRS resource isindicated by an SRS resource indicator field of a downlink controlinformation (DCI) and the UE is configured with at least one SRSresource for a configured transmission scheme via a higher layerparameter in the RRC message; and control transmission of a physicaluplink shared channel (PUSCH) scheduled by the DCI in a correspondingphysical uplink control channel (PUCCH) resource with a lowest resourceidentifier (ID) within an active uplink (UL) bandwidth part (BWP) whenthe UE is not configured with the at least one SRS resource indicated bythe SRS resource indicator field of the DCI.

Examples 15 includes the SoC of example 14 and/or some other examplesherein, wherein the configured transmission scheme is a codebook basedtransmission scheme or a non-codebook based transmission scheme, and thePUSCH is a codebook based transmission or a non-codebook basedtransmission.

Examples 16 includes the SoC of examples 14-15 and/or some otherexamples herein, wherein a DCI format of the received DCI is DCI format0_0, and the baseband circuitry is arranged to: control transmission ofthe PUSCH in the corresponding PUCCH resource with the lowest resourceID within the active UL BWP.

Examples 17 includes the SoC of examples 14-16 and/or some otherexamples herein, wherein a DCI format of the received DCI is DCI format0_1 or DCI format 1_1 that includes an SRS request field, and thebaseband circuitry is arranged to: control transmission of an SRS in aconfigured SRS resource based on measurement of an associated NZP CSI-RSto be transmitted in the NZP CSI-RS resources when the configured SRSresource is indicated by the SRS request field of the DCI, the UE isconfigured with the SRS resource for a non-codebook based transmissionscheme, and the configured SRS resource is among an aperiodic SRSresource set.

Examples 18 includes the SoC of examples 14-16 and/or some otherexamples herein, wherein the RRC message is to include an SRSconfiguration (SRS-Config), the SRS-Config to include one or moresounding reference signal resource sets (SRS-ResourceSets), eachSRS-ResourceSet of the one or more SRS-ResourceSets to indicate one ormore SRS resources, and the one or more SRS resources of eachSRS-ResourceSet are configured to be used for one of periodic SRStransmissions, semi-persistent SRS transmissions, or aperiodic SRStransmissions.

Examples 19 includes the SoC of example 18 and/or some other examplesherein, wherein at least one SRS-ResourceSet of the one or moreSRS-ResourceSets includes one or more SRS resources configured to beused for semi-persistent SRS transmissions, and the baseband circuitryis arranged to: use a same spatial domain filter to transmit the PUSCHas the at least one configured SRS resource indicated by the receivedDCI when the at least one configured SRS resource indicated by thereceived DCI is among the one or more SRS resources configured to beused for semi-persistent SRS transmissions.

Examples 20 includes the SoC of examples 18-19 and/or some otherexamples herein, wherein the SRS-Config is to include a spatial relation(spatialRelationInfo) configuration to indicate a spatial relationbetween a reference RS and a target SRS, at least one SRS-ResourceSet ofthe one or more SRS-ResourceSets includes one or more SRS resourcesconfigured to be used for semi-persistent SRS transmissions, and thebaseband circuitry is arranged to: use a same spatial domain filter totransmit the PUSCH as the at least one configured SRS resource indicatedby the spatialRelationInfo configuration when the at least oneconfigured SRS resource is among the one or more SRS resourcesconfigured to be used for semi-persistent SRS transmissions, and the atleast one configured SRS resource is not indicated by the received DCI.

Examples 21 includes an apparatus to operate as a Radio Access Network(RAN) node, the apparatus comprising: processor circuitry arranged to:generate a radio resource control (RRC) message to configure a userequipment (UE) with a sounding reference signal resource set(SRS-ResourceSet), generate a first downlink control information (DCI)to indicate an SRS resource (SRS-Resource) in the configuredSRS-ResourceSet, the first DCI to trigger the UE to transmit an SRS inthe indicated SRS-Resource, and generate a second DCI to not indicate anSRS resource in the configured SRS-ResourceSet, the second DCI totrigger the UE to transmit a physical uplink shared channel (PUSCH)scheduled by a DCI in a corresponding physical uplink control channel(PUCCH) resource with a lowest resource identifier (ID) within an activeuplink (UL) bandwidth part (BWP); and communication circuitrycommunicatively coupled with the processor circuitry, the communicationcircuitry arranged to transmit the RRC message to the UE, and transmitthe first DCI or the second DCI to the UE.

Examples 22 includes the apparatus of example 21 and/or some otherexamples herein, wherein the processor circuitry is arranged to set ausage of the SRS-ResourceSet to “Codebook”, and generate the first DCIto indicate the SRS-Resource in an SRS request field iof the first DCI.

Examples 23 includes the apparatus of example 21 and/or some otherexamples herein, wherein the processor circuitry is arranged to set ausage of the SRS-ResourceSet to “nonCodebook”, and generate the secondDCI to indicate the SRS-Resource in an SRS resource indicator field ofthe second DCI.

Examples 24 includes the apparatus of example 21 and/or some otherexamples herein, wherein a DCI format of the second DCI is DCI format0_0, and the DCI format of the first DCI is DCI format 0_1 or DCI format1_1.

Examples 25 includes the apparatus of example 21 and/or some otherexamples herein, wherein the processor circuitry is arranged to:generate the RRC message to include an SRS configuration (SRS-Config)and an a non-zero power channel state information reference signalresource set (NZP-CSI-RS-ResourceSet), wherein the SRS-Config is toinclude the SRS-ResourceSet, and SRS-Resources of the SRS-ResourceSetare configured to be used for one of periodic SRS transmissions,semi-persistent SRS transmissions, or aperiodic SRS transmissions,wherein the NZP-CSI-RS-ResourceSet is to indicate one or more non-zeropower channel state information reference signal (NZP CSI-RS) resources,wherein same antenna ports are to be used for the NZP CSI-RS resourcesin the NZP-CSI-RS-ResourceSet having a same port index when theNZP-CSI-RS-ResourceSet includes a trs-Info parameter set to ‘on’,wherein the NZP CSI-RS resources in the NZP-CSI-RS-ResourceSet are to betransmitted with a same downlink spatial domain transmission filter whenthe NZP-CSI-RS-ResourceSet includes a repetition parameter set to ‘on’,and wherein only one of the trs-Info or the repetition can be configuredby the NZP-CSI-RS-ResourceSet.

Examples 26 includes a method to be performed by a user equipment (UE),the method comprising: receiving a radio resource control (RRC) message,the RRC message to include a non-zero power channel state informationreference signal resource set (NZP-CSI-RS-ResourceSet), and theNZP-CSI-RS-ResourceSet to indicate one or more non-zero power channelstate information reference signal (NZP CSI-RS) resources; assuming orcausing to assume same antenna ports are to be used for the NZP CSI-RSresources in the NZP-CSI-RS-ResourceSet having a same port index whenthe NZP-CSI-RS-ResourceSet includes a trs-Info parameter set to ‘on’;and assuming or causing that the NZP CSI-RS resources in theNZP-CSI-RS-ResourceSet are to be transmitted with a same downlinkspatial domain transmission filter when the NZP-CSI-RS-ResourceSetincludes a repetition parameter set to ‘on’, wherein only one of thetrs-Info or the repetition can be configured by theNZP-CSI-RS-ResourceSet.

Examples 27 includes the method of example 26 and/or some other examplesherein, wherein the NZP-CSI-RS-ResourceSet is to include aQCL-Info-PeriodicCSI-RS parameter to indicate a transmission beam forindividual ones of the one or more NZP CSI-RS resources.

Examples 28 includes the method of examples 26-27 and/or some otherexamples herein, wherein the method comprises: receiving a downlinkcontrol information (DCI), the DCI to include an SRS resource indicatorfield; transmitting a sounding reference signal (SRS) in at least oneconfigured SRS resource when the at least one configured SRS resource isindicated by the SRS resource indicator field of the DCI and the UE isconfigured with at least one SRS resource for a configured transmissionscheme via a higher layer parameter in the RRC message; and transmittinga physical uplink shared channel (PUSCH) scheduled by the DCI in acorresponding physical uplink control channel (PUCCH) resource with alowest resource identifier (ID) within an active uplink (UL) bandwidthpart (BWP) when the UE is not configured with the at least one SRSresource indicated by the SRS resource indicator field of the DCI.

Examples 29 includes the method of example 28 and/or some other examplesherein, wherein the configured transmission scheme is a codebook basedtransmission scheme or a non-codebook based transmission scheme, and thePUSCH is a codebook based transmission or a non-codebook basedtransmission.

Examples 30 includes the method of examples 28-29 and/or some otherexamples herein, wherein a DCI format of the received DCI is DCI format0_0, and wherein the method comprises: transmitting the PUSCH in thecorresponding PUCCH resource with the lowest resource ID within theactive UL BWP.

Examples 31 includes the method of examples 28-30 and/or some otherexamples herein, wherein a DCI format of the received DCI is DCI format0_1 or DCI format 1_1 that includes an SRS request field, and whereinthe method comprises: transmitting an SRS in a configured SRS resourcebased on measurement of an associated NZP CSI-RS to be transmitted inthe NZP CSI-RS resources when the configured SRS resource is indicatedby the SRS request field of the DCI, the UE is configured with the SRSresource for a non-codebook based transmission scheme, and theconfigured SRS resource is among an aperiodic SRS resource set.

Examples 32 includes the method of examples 28-31 and/or some otherexamples herein, wherein the RRC message is to include an SRSconfiguration (SRS-Config), the SRS-Config to include one or moresounding reference signal resource sets (SRS-ResourceSets), eachSRS-ResourceSet of the one or more SRS-ResourceSets to indicate one ormore SRS resources, and the one or more SRS resources of eachSRS-ResourceSet are configured to be used for one of periodic SRStransmissions, semi-persistent SRS transmissions, or aperiodic SRStransmissions.

Examples 33 includes the method of example 32 and/or some other examplesherein, wherein at least one SRS-ResourceSet of the one or moreSRS-ResourceSets includes one or more SRS resources configured to beused for semi-persistent SRS transmissions, and wherein the methodcomprises: using a same spatial domain filter to transmit the PUSCH asthe at least one configured SRS resource indicated by the received DCIwhen the at least one configured SRS resource indicated by the receivedDCI is among the one or more SRS resources configured to be used forsemi-persistent SRS transmissions.

Examples 34 includes the method of examples 32-33 and/or some otherexamples herein, wherein the SRS-Config is to include a spatial relation(spatialRelationInfo) configuration to indicate a spatial relationbetween a reference RS and a target SRS, at least one SRS-ResourceSet ofthe one or more SRS-ResourceSets includes one or more SRS resourcesconfigured to be used for semi-persistent SRS transmissions, and whereinthe method comprises: using a same spatial domain filter to transmit thePUSCH as the at least one configured SRS resource indicated by thespatialRelationInfo configuration when the at least one configured SRSresource is among the one or more SRS resources configured to be usedfor semi-persistent SRS transmissions, and the at least one configuredSRS resource is not indicated by the received DCI.

Examples 35 includes a method to be performed by a user equipment (UE),the method comprising: transmitting an SRS in the at least oneconfigured SRS resource when the UE is configured with at least onesounding reference signal (SRS) resource for a configured transmissionscheme via a higher layer parameter and the at least one configured SRSresource is indicated by a received downlink control information (DCI)or Radio Resource Control (RRC) message; and transmitting, when the UEis not configured with at least one SRS resource, a physical uplinkshared channel (PUSCH) scheduled by a DCI in a corresponding physicaluplink control channel (PUCCH) resource with a lowest resourceidentifier (ID) within an active uplink (UL) bandwidth part (BWP).

Examples 36 includes the method of example 35 and/or some other examplesherein, wherein the PUSCH is a codebook based transmission or anon-codebook based transmission.

Examples 37 includes the method of examples 35-36 and/or some otherexamples herein, wherein a DCI format of the received DCI is DCI format0_0 when the UE is not configured with at least one SRS resource, andthe DCI format of the received DCI is DCI format 0_1 or DCI format 1_1when the UE is configured with at least one SRS resource.

Examples 38 includes the method of example 37 and/or some other examplesherein, when the DCI is the DCI format 0_0, the method comprises:transmitting the PUSCH in the corresponding PUCCH resource with thelowest resource ID within the active UL BWP.

Examples 39 includes the method of examples 35-38 and/or some otherexamples herein, wherein the method comprises: receiving a radioresource control (RRC) message, the RRC message to include an SRSconfiguration (SRS-Config), the SRS-Config to include one or moresounding reference signal resource sets (SRS-ResourceSets), eachSRS-ResourceSet of the one or more SRS-ResourceSets to indicate one ormore SRS resources, and the one or more SRS resources of eachSRS-ResourceSet are configured to be used for one of periodic SRStransmissions, semi-persistent SRS transmissions, or aperiodic SRStransmissions.

Examples 40 includes the method of example 39 and/or some other examplesherein, wherein at least one SRS-ResourceSet of the one or moreSRS-ResourceSets includes the at least one configured SRS resource.

Examples 41 includes the method of example 40 and/or some other examplesherein, wherein the at least one configured SRS resource is configuredto be used for aperiodic SRS transmissions, and the received DCIincludes an SRS request field indicating the at least one configured SRSresource to trigger transmission of the aperiodic SRS, wherein only oneSRS resource within the SRS-ResourceSet configuration can be triggered.

Examples 42 includes the method of examples 39-41 and/or some otherexamples herein, wherein at least one SRS-ResourceSet of the one or moreSRS-ResourceSets includes one or more SRS resources configured to beused for semi-persistent SRS transmissions, and wherein the methodcomprises: using a same spatial domain filter to transmit the PUSCH asthe at least one configured SRS resource indicated by the received DCIwhen the at least one configured SRS resource indicated by the receivedDCI is among the one or more SRS resources configured to be used forsemi-persistent SRS transmissions.

Examples 43 includes the method of examples 39-42 and/or some otherexamples herein, wherein the SRS-Config is to include a spatial relation(spatialRelationInfo) configuration to indicate a spatial relationbetween a reference RS and a target SRS, at least one SRS-ResourceSet ofthe one or more SRS-ResourceSets includes one or more SRS resourcesconfigured to be used for semi-persistent SRS transmissions, and whereinthe method comprises: using a same spatial domain filter to transmit thePUSCH as the at least one configured SRS resource indicated by thespatialRelationInfo configuration when the at least one configured SRSresource is among the one or more SRS resources configured to be usedfor semi-persistent SRS transmissions, and the at least one configuredSRS resource is not indicated by the received DCI.

Examples 44 includes the method of examples 39-43 and/or some otherexamples herein, wherein the RRC message is to include a non-zero powerchannel state information reference signal resource set(NZP-CSI-RS-ResourceSet), and the NZP-CSI-RS-ResourceSet is to indicateone or more non-zero power channel state information reference signal(NZP CSI-RS) resources, and wherein the method comprises: assuming sameantenna ports are to be used for the NZP CSI-RS resources in theNZP-CSI-RS-ResourceSet having a same port index when theNZP-CSI-RS-ResourceSet includes a trs-Info parameter set to ‘on’; andassuming that the NZP CSI-RS resources in the NZP-CSI-RS-ResourceSet areto be transmitted with a same downlink spatial domain transmissionfilter when the NZP-CSI-RS-ResourceSet includes a repetition parameterset to ‘on’, wherein only one of the trs-Info or the repetition can beconfigured by the NZP-CSI-RS-ResourceSet.

Examples 45 includes the method of example 44 and/or some other examplesherein, wherein the NZP-CSI-RS-ResourceSet is to include aQCL-Info-PeriodicCSI-RS parameter to indicate a transmission beam forindividual ones of the one or more NZP CSI-RS resources.

Examples 46 includes one or more computer-readable storage media (CRSM)comprising instructions, wherein execution of the instructions by one ormore processors of a user equipment (UE) is to cause the UE to performthe method of any one or more of examples 26-45 and/or some otherexamples herein.

Examples 47 includes a method to be performed by a Radio Access Network(RAN) node, the method comprising: generating a radio resource control(RRC) message to configure a user equipment (UE) with a soundingreference signal resource set (SRS-ResourceSet); transmitting the RRCmessage to the UE; generating a first downlink control information (DCI)to indicate an SRS resource (SRS-Resource) in the configuredSRS-ResourceSet, the first DCI to trigger the UE to transmit an SRS inthe indicated SRS-Resource; generating a second DCI to not indicate anSRS resource in the configured SRS-ResourceSet, the second DCI totrigger the UE to transmit a physical uplink shared channel (PUSCH)scheduled by a DCI in a corresponding physical uplink control channel(PUCCH) resource with a lowest resource identifier (ID) within an activeuplink (UL) bandwidth part (BWP); and transmitting the first DCI or thesecond DCI to the UE.

Examples 48 includes the method of example 47 and/or some other examplesherein, wherein the method comprises setting a usage of theSRS-ResourceSet to “Codebook”; and generating the first DCI to indicatethe SRS-Resource in an SRS request field iof the first DCI.

Examples 49 includes the method of examples 47-48 and/or some otherexamples herein, wherein the method comprises setting a usage of theSRS-ResourceSet to “nonCodebook”; and generating the second DCI toindicate the SRS-Resource in an SRS resource indicator field of thesecond DCI.

Examples 50 includes the method of examples 47-49 and/or some otherexamples herein, wherein a DCI format of the second DCI is DCI format0_0, and the DCI format of the first DCI is DCI format 0-1 or DCI format1_1.

Examples 51 includes the method of examples 47-50 and/or some otherexamples herein, wherein the method comprises: generating the RRCmessage to include an SRS configuration (SRS-Config) and an a non-zeropower channel state information reference signal resource set(NZP-CSI-PS-ResourceSet), wherein the SRS-Config is to include theSRS-ResourceSet, and SRS-Resources of the SRS-ResourceSet are configuredto be used for one of periodic SRS transmissions, semi-persistent SRStransmissions, or aperiodic SRS transmissions, wherein theNZP-CSI-RS-ResourceSet is to indicate one or more non-zero power channelstate information reference signal (NZP CSI-RS) resources, wherein sameantenna ports are to be used for the NZP CSI-RS resources in theNZP-CSI-RS-ResourceSet having a same port index when theNZP-CSI-RS-ResourceSet includes a trs-Info parameter set to ‘on’,wherein the NZP CSI-RS resources in the NZP-CSI-RS-ResourceSet are to betransmitted with a same downlink spatial domain transmission filter whenthe NZP-CSI-RS-ResourceSet includes a repetition parameter set to ‘on’,and wherein only one of the trs-Info or the repetition can be configuredby the NZP-CSI-RS-ResourceSet.

Examples 52 includes one or more computer-readable storage media (CRSM)comprising instructions, wherein execution of the instructions by one ormore processors of a Radio Access Network (RAN) node is to cause the RANnode to perform the method of any one or more of examples 47-51 and/orsome other examples herein

Example 53 may include an apparatus comprising means to perform one ormore elements of a method described in or related to any of examples1-52, or any other method or process described herein.

Example 54 may include one or more non-transitory computer-readablemedia comprising instructions to cause an electronic device, uponexecution of the instructions by one or more processors of theelectronic device, to perform one or more elements of a method describedin or related to any of examples 1-52, or any other method or processdescribed herein.

Example 55 may include an apparatus comprising logic, modules, orcircuitry to perform one or more elements of a method described in orrelated to any of examples 1-52, or any other method or processdescribed herein.

Example 56 may include a method, technique, or process as described inor related to any of examples 1-52, or portions or parts thereof.

Example 57 may include an apparatus comprising: one or more processorsand one or more computer-readable media comprising instructions that,when executed by the one or more processors, cause the one or moreprocessors to perform the method, techniques, or process as described inor related to any of examples 1-52, or portions thereof.

Example 58 may include a signal as described in or related to any ofexamples 1-52, or portions or parts thereof.

Example 59 includes a packet, frame, segment, protocol data unit (PDU),or message as described in or related to any of examples 1-52, orportions or parts thereof, or otherwise described in the presentdisclosure

Example 60 may include a signal in a wireless network as shown anddescribed herein.

Example 61 may include a method of communicating in a wireless networkas shown and described herein.

Example 62 may include a system for providing wireless communication asshown and described herein.

Example 63 may include a device for providing wireless communication asshown and described herein.

Any of the above-described examples may be combined with any otherexample (or combination of examples), unless explicitly statedotherwise. The foregoing description of one or more implementationsprovides illustration and description, but is not intended to beexhaustive or to limit the scope of embodiments to the precise formdisclosed. Modifications and variations are possible in light of theabove teachings or may be acquired from practice of various embodiments.

The present disclosure has been described with reference to flowchartillustrations and/or block diagrams of methods, apparatus (systems),and/or computer program products according to embodiments of the presentdisclosure. In the drawings, some structural or method features may beshown in specific arrangements and/or orderings. However, it should beappreciated that such specific arrangements and/or orderings may not berequired. Rather, in some embodiments, such features may be arranged ina different manner and/or order than shown in the illustrative figures.Additionally, the inclusion of a structural or method feature in aparticular figure is not meant to imply that such feature is required inall embodiments and, in some embodiments, may not be included or may becombined with other features.

The flowchart and block diagrams in the figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present disclosure. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the disclosure.As used herein, the singular forms “a,” “an” and “the” are intended toinclude plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specific thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operation, elements,components, and/or groups thereof.

For the purposes of the present disclosure, the phrase “A and/or B”means (A), (B), or (A and B). For the purposes of the presentdisclosure, the phrase “A, B, and/or C” means (A), (B), (C), (A and B),(A and C), (B and C), or (A, B and C). The description may use thephrases “in an embodiment,” or “In some embodiments,” which may eachrefer to one or more of the same or different embodiments. Furthermore,the terms “comprising,” “including,” “having,” and the like, as usedwith respect to embodiments of the present disclosure, are synonymous.

The terms “coupled,” “communicatively coupled,” along with derivativesthereof are used herein. The term “coupled” may mean two or moreelements are in direct physical or electrical contact with one another,may mean that two or more elements indirectly contact each other butstill cooperate or interact with each other, and/or may mean that one ormore other elements are coupled or connected between the elements thatare said to be coupled with each other. The term “directly coupled” maymean that two or more elements are in direct contact with one another.The term “communicatively coupled” may mean that two or more elementsmay be in contact with one another by a means of communication includingthrough a wire or other interconnect connection, through a wirelesscommunication channel or ink, and/or the like.

As used herein, the term “circuitry” refers to a circuit or system ofmultiple circuits configured to perform a particular function in anelectronic device. The circuit or system of circuits may be part of, orinclude one or more hardware components, such as a logic circuit, aprocessor (shared, dedicated, or group) and/or memory (shared,dedicated, or group), ASICs, FPDs (e.g., FPGAs, PLDs, CPLDs, HCPLDs, astructured ASICs, or a programmable SoCs, DSPs, etc., that areconfigured to provide the described functionality. In addition, the term“circuitry” may also refer to a combination of one or more hardwareelements with the program code used to carry out the functionality ofthat program code. Some types of circuitry may execute one or moresoftware or firmware programs to provide at least some of the describedfunctionality. Such a combination of hardware elements and program codemay be referred to as a particular type of circuitry.

As used herein, the term “processor circuitry” refers to, is part of, orincludes circuitry capable of sequentially and automatically carryingout a sequence of arithmetic or logical operations, or recording,storing, and/or transferring digital data. and/or any other devicecapable of executing or otherwise operating computer-executableinstructions, such as program code, software modules, and/or functionalprocesses.

As used herein, the term “module” refers to one or more independentelectronic circuits packaged onto a circuit board, SoC, SiP, etc.,configured to provide a basic function within a computer system.

As used herein, the term “module” refers to, be part of, or include anFPD, ASIC, a processor (shared, dedicated, or group) and/or memory(shared, dedicated, or group), etc., that execute one or more softwareor firmware programs, a combinational logic circuit, and/or othersuitable components that provide the described functionality.

As used herein, the term “interface circuitry” refers to, is part of, orincludes circuitry providing for the exchange of information between twoor more components or devices. The term “interface circuitry” refers toone or more hardware interfaces, for example, buses, input/output (I/O)interfaces, peripheral component interfaces, network interface cards,and/or the like.

As used herein, the term “device” refers to a physical entity embeddedinside, or attached to, another physical entity in its vicinity, withcapabilities to convey digital information from or to that physicalentity. As used herein, the term “element” refers to a unit that isindivisible at a given level of abstraction and has a clearly definedboundary, wherein an element may be any type of entity. As used herein,the term “controller” refers to an element or entity that has thecapability to affect a physical entity, such as by changing its state orcausing the physical entity to move. As used herein, the term “entity”refers to (1) a distinct component of an architecture or device, or (2)information transferred as a payload. The term “network element” as usedherein refers to physical or virtualized equipment and/or infrastructureused to provide wired or wireless communication network services. Theterm “network element” may be considered synonymous to and/or referredto as a networked computer, networking hardware, network equipment,network node, router, switch, hub, bridge, radio network controller, RANdevice, RAN node, gateway, server, virtualized VNF, NFVI, and/or thelike.

As used herein, the term “computer system” refers to any typeinterconnected electronic devices, computer devices, or componentsthereof. Additionally, the term “computer system” and/or “system” refersto various components of a computer that are communicatively coupledwith one another, or otherwise organized to accomplish one or morefunctions. Furthermore, the term “computer system” and/or “system”refers to multiple computer devices and/or multiple computing systemsthat are communicatively coupled with one another and configured toshare computing and/or networking resources.

As used herein, the term “architecture” refers to a fundamentalorganization of a system embodied in its components, their relationshipsto one another, and to an environment, as well as to the principlesguiding its design and evolution.

As used herein, the term “appliance,” “computer appliance,” or the like,refers to a discrete hardware device with integrated program code (e.g.,software or firmware) that is specifically or specially designed toprovide a specific computing resource. A “virtual appliance” is avirtual machine image to be implemented by a hypervisor-equipped devicethat virtualizes or emulates a computer appliance or otherwise isdedicated to provide a specific computing resource.

As used herein, the term “user equipment” or “UE” as used herein refersto a device with radio communication capabilities and may describe aremote user of network resources in a communications network. The term“user equipment” or “UE” may be considered synonymous to, and may bereferred to as, client, mobile, mobile device, mobile terminal, userterminal, mobile unit, mobile station, mobile user, subscriber, user,remote station, access agent, user agent, receiver, radio equipment,reconfigurable radio equipment, reconfigurable mobile device, etc.Furthermore, the term “user equipment” or “UE” may include any type ofwireless/wired device or any computing device including a wirelesscommunications interface.

As used herein, the term “channel” as used herein refers to anytransmission medium, either tangible or intangible, which is used tocommunicate data or a data stream. The term “channel” may be synonymouswith and/or equivalent to “communications channel,” “data communicationschannel,” “transmission channel,” “data transmission channel,” “accesschannel,” “data access channel,” “link,” “data link,” “carrier,”“radiofrequency carrier,” and/or any other like term denoting a pathwayor medium through which data is communicated. Additionally, the term“link” as used herein refers to a connection between two devices througha RAT for the purpose of transmitting and receiving information.

As used herein, the terms “instantiate,” “instantiation,” and the likerefers to the creation of an instance, and an “instance” refers to aconcrete occurrence of an object, which may occur, for example, duringexecution of program code.

As used herein, a “database object”, “data object”, or the like refersto any representation of information in a database that is in the formof an object, attribute-value pair (AVP), key-value pair (KVP), tuple,etc., and may include variables, data structures, functions, methods,classes, database records, database fields, database entities,associations between data and database entities (also referred to as a“relation”), and the like.

As used herein, the term “resource” refers to a physical or virtualdevice, a physical or virtual component within a computing environment,and/or a physical or virtual component within a particular device, suchas computer devices, mechanical devices, memory space, processor/CPUtime, processor/CPU usage, processor and accelerator loads, hardwaretime or usage, electrical power, input/output operations, ports ornetwork sockets, channel/link allocation, throughput, memory usage,storage, network, database and applications, workload units, and/or thelike. The term “network resource” refers to a resource hosted by aremote entity (e.g., a cloud computing service) and accessible over anetwork. The term “on-device resource” refers to a resource hostedinside a device and enabling access to the device, and thus, to therelated physical entity. System resources may be considered as a set ofcoherent functions, network data objects or services, accessible througha server where such system resources reside on a single host or multiplehosts and are clearly identifiable. Additionally, a “virtualizedresource” refers to compute, storage, and/or network resources providedby virtualization infrastructure to an application, such as amulti-access edge applications. The term “information element” refers toa structural element containing one or more fields. The term “field”refers to individual contents of an information element, or a dataelement that contains content.

For the purposes of the present document, the abbreviations listed intable ABBR may apply to the examples and embodiments discussed herein.

TABLE ABBR 3GPP Third Generation Partnership Project 4G FourthGeneration 5G Fifth Generation 5GC 5G Core network ACK AcknowledgementAF Application Function AM Acknowledged Mode AMBR Aggregate Maximum BitRate AMF Access and Mobility Management Function AN Access Network ANRAutomatic Neighbor Relation AP Application Protocol, Antenna Port,Access Point API Application Programming Interface APN Access Point NameARP Allocation and Retention Priority ARQ Automatic Repeat Request ASAccess Stratum ASN.1 Abstract Syntax Notation One AUSF AuthenticationServer Function AWGN Additive White Gaussian Noise BCH Broadcast ChannelBER Bit Error Ratio BLER Block Error Rate BPSK Binary Phase Shift KeyingBRAS Broadband Remote Access Server BSS Business Support System BS BaseStation BSR Buffer Status Report BW Bandwidth BWP Bandwidth Part C-RNTICell Radio Network Temporary Identity CA Carrier Aggregation,Certification Authority CAPEX CAPital EXpenditure CBRA Contention BasedRandom Access CC Component Carrier, Country Code, Cryptographic ChecksumCCA Clear Channel Assessment CCE Control Channel Element CCCH CommonControl Channel CE Coverage Enhancement CDM Content Delivery NetworkCDMA Code-Division Multiple Access CFRA Contention Free Random Access CGCell Group CI Cell Identity CID Cell-ID (e.g., positioning method) CIMCommon Information Model CIR Carrier to Interference Ratio CK Cipher KeyCM Connection Management, Conditional Mandatory CMAS Commercial MobileAlert Service CMD Command CMS Cloud Management System CO ConditionalOptional CoMP Coordinated Multi-Point CORESET Control Resource Set COTSCommercial Off-The-Shelf CP Control Plane, Cyclic Prefix, ConnectionPoint CPD Connection Point Descriptor CPE Customer Premise EquipmentCPICH Common Pilot Channel CQI Channel Quality Indicator CPU CSIprocessing unit, Central Processing Unit C/R Command/Response field bitCRAN Cloud Radio Access Network, Cloud RAN CRB Common Resource Block CRCCyclic Redundancy Check CRI Channel-State Information ResourceIndicator, CSI-RS Resource Indicator C-RNTI Cell RNTI CS CircuitSwitched CSAR Cloud Service Archive CSI Channel-State Information CSI-IMCSI Interference Measurement CSI-RS CSI Reference Signal CSI-RSRP CSIreference signal received power CSI-RSRQ CSI reference signal receivedquality CSI-SINR CSI signal-to-noise and interference ratio CSMA CarrierSense Multiple Access CSMA/CA CSMA with collision avoidance CSS CommonSearch Space, Cell-specific Search Space CTS Clear-to-Send CW CodewordCWS Contention Window Size D2D Device-to-Device DC Dual Connectivity,Direct Current DCI Downlink Control Information DF Deployment Flavour DLDownlink DMTF Distributed Management Task Force DPDK Data PlaneDevelopment Kit DM-RS, DMRS Demodulation Reference Signal DN Datanetwork DRB Data Radio Bearer DRS Discovery Reference Signal DRXDiscontinuous Reception DSL Domain Specific Language. Digital SubscriberLine DSLAM DSL Access Multiplexer DwPTS Downlink Pilot Time Slot E-LANEthernet Local Area Network E2E End-to-End ECCA extended clear channelassessment, extended CCA ECCE Enhanced Control Channel Element, EnhancedCCE ED Energy Detection EDGE Enhanced Datarates for GSM Evolution (GSMEvolution) EGMF Exposure Governance Management Function EGPRS EnhancedGPRS EIR Equipment Identity Register eLAA enhanced Licensed AssistedAccess, enhanced LAA EM Element Manager eMBB enhanced Mobile BroadbandeMBMS Evolved MBMS EMS Element Management System eNB evolved NodeB,E-UTRAN Node B EN-DC E-UTRA-NR Dual Connectivity EPC Evolved Packet CoreEPDCCH enhanced PDCCH, enhanced Physical Downlink Control Cannel EPREEnergy per resource element EPS Evolved Packet System EREG enhanced REG,enhanced resource element groups ETSI European TelecommunicationsStandards Institute ETWS Earthquake and Tsunami Warning System eUICCembedded UICC, embedded Universal Integrated Circuit Card E-UTRA EvolvedUTRA E-UTRAN Evolved UTRAN F1AP F1 Application Protocol F1-C F1 Controlplane interface F1-U F1 User plane interface FACCH Fast AssociatedControl CHannel FACCH/F Fast Associated Control Channel/Full rateFACCH/H Fast Associated Control Channel/Half rate FACH Forward AccessChannel FAUSCH Fast Uplink Signalling Channel FB Functional Block FBIFeedback Information FCC Federal Communications Commission FCCHFrequency Correction CHannel FDD Frequency Division Duplex FDM FrequencyDivision Multiplex FDMA Frequency Division Multiple Access FE Front EndFEC Forward Error Correction FFS For Further Study FFT Fast FourierTransformation feLAA further enhanced Licensed Assisted Access, furtherenhanced LAA FN Frame Number FPGA Field-Programmable Gate Array FRFrequency Range G-RNTI GERAN Radio Network Temporary Identity GERAN GSMEDGE RAN, GSM EDGE Radio Access Network GGSN Gateway GPRS Support NodeGLONASS GLObal’naya NAvigatsionnaya Sputnikovaya Sistema (Engl.: GlobalNavigation Satellite System) gNB Next Generation NodeB gNB-CUgNB-centralized unit, Next Generation NodeB centralized unit gNB-DUgNB-distributed unit, Next Generation NodeB distributed unit GNSS GlobalNavigation Satellite System GPRS General Packet Radio Service GSM GlobalSystem for Mobile Communications, Groupe Spécial Mobile GTP GPRSTunneling Protocol GTP-U GPRS Tunnelling Protocol for User Plane GUMMEIGlobally Unique MME Identifier GUTI Globally Unique Temporary UEIdentity HARQ Hybrid ARQ, Hybrid Automatic Repeat Request HANDO, HOHandover HFN HyperFrame Number HHO Hard Handover HLR Home LocationRegister HN Home Network HPLMN Home Public Land Mobile Network HSDPAHigh Speed Downlink Packet Access HSN Hopping Sequence Number HSPA HighSpeed Packet Access HSS Home Subscriber Server HSUPA High Speed UplinkPacket Access HTTP Hyper Text Transfer Protocol HTTPS Hyper TextTransfer Protocol Secure (https is http/1.1 over SSL, i.e. port 443)I-Block Information Block ICCID Integrated Circuit Card IdentificationICIC Inter-Cell Interference Coordination ID Identity, identifier IDFTInverse Discrete Fourier Transform IE Information element IEEE Instituteof Electrical and Electronics Engineers IEI Information ElementIdentifier IEIDL Information Element Identifier Data Length IETFInternet Engineering Task Force IF Infrastructure IM InterferenceMeasurement, Intermodulation, IP Multimedia IMC IMS Credentials IMEIInternational Mobile Equipment Identity IMGI International mobile groupidentity IMPI IP Multimedia Private Identity IMPU IP Multimedia PUblicidentity IMS IP Multimedia Subsystem IMSI International MobileSubscriber Identity IoT Internet of Things IP Internet Protocol Ipsec IPSecurity, Internet Protocol Security IP-CAN IP-Connectivity AccessNetwork IP-M IP Multicast IPv4 Internet Protocol Version 4 IPv6 InternetProtocol Version 6 IR Infrared IRP Integration Reference Point ISDNIntegrated Services Digital Network ISIM IM Services Identity Module ISOInternational Organisation for Standardisation ISP Internet ServiceProvider IWF Interworking-Function I-WLAN Interworking WLAN K Constraintlength of the convolutional code, USIM Individual key kB Kilobyte (1000bytes) kbps kilo-bits per second Kc Ciphering key Ki Individualsubscriber authentication key KPI Key Performance Indicator KQI KeyQuality Indicator KSI Key Set Identifier ksps kilo-symbols per secondKVM Kernel Virtual Machine L1 Layer 1 (physical layer) L1-RSRP Layer 1reference signal received power L2 Layer 2 (data link layer) L3 Layer 3(network layer) LAA Licensed Assisted Access LAN Local Area Network LBTListen Before Talk LCM LifeCycle Management LCR Low Chip Rate LCSLocation Services LI Layer Indicator LLC Logical Link Control, Low LayerCompatibility LPLMN Local PLMN LPP LTE Positioning Protocol LSB LeastSignificant Bit LTE Long Term Evolution LWA LTE-WLAN aggregation LWIPLTE/WLAN Radio Level Integration with IPsec Tunnel LTE Long TermEvolution M2M Machine-to-Machine MAC Medium Access Control (protocollayering context) MAC Message authentication code (security/encryptioncontext) MAC-A MAC used for authentication and key agreement (TSG T WG3context) MAC-I MAC used for data integrity of signalling messages (TSG TWG3 context) MANO Management and Orchestration MBMS Multimedia Broadcastand Multicast Service MBSFN Multimedia Broadcast multicast serviceSingle Frequency Network MCC Mobile Country Code MCG Master Cell GroupMCOT Maximum Channel Occupancy Time MCS Modulation and coding schemeMDAF Management Data Analytics Function MDAS Management Data AnalyticsService MDT Minimization of Drive Tests ME Mobile Equipment MeNB mastereNB MER Message Error Ratio MGL Measurement Gap Length MGRP MeasurementGap Repetition Period MIB Master Information Block, ManagementInformation Base MIMO Multiple Input Multiple Output MLC Mobile LocationCentre MM Mobility Management MME Mobility Management Entity MN MasterNode MO Measurement Object, Mobile Originated MPBCH MTC PhysicalBroadcast CHannel MPDCCH MTC Physical Downlink Control CHannel MPDSCHMTC Physical Downlink Shared CHannel MPRACH MTC Physical Random AccessCHannel MPUSCH MTC Physical Uplink Shared Channel MPLS MultiProtocolLabel Switching MS Mobile Station MSB Most Significant Bit MSC MobileSwitching Centre MSI Minimum System Information, MCH SchedulingInformation MSID Mobile Station Identifier MSIN Mobile StationIdentification Number MSISDN Mobile Subscriber ISDN Number MT MobileTerminated, Mobile Termination MTC Machine-Type Communications mMTCmassive MTC, massive Machine-Type Communications MU-MIMO Multi User MIMOMWUS MTC wake-up signal, MTC WUS NACK Negative Acknowledgement NAINetwork Access Identifier NAS Non-Access Stratum, Non-Access Stratumlayer NCT Network Connectivity Topology NEC Network Capability ExposureNE-DC NR-E-UTRA Dual Connectivity NEF Network Exposure Function NFNetwork Function NFP Network Forwarding Path NFPD Network ForwardingPath Descriptor NFV Network Functions Virtualization NFVI NFVInfrastructure NFVO NFV Orchestrator NG Next Generation, Next GenNGEN-DC NG-RAN E-UTRA-NR Dual Connectivity NM Network Manager NMSNetwork Management System N-PoP Network Point of Presence NMIB, N-MIBNarrowband MIB NPBCH Narrowband Physical Broadcast CHannel NPDCCHNarrowband Physical Downlink Control CHannel NPDSCH Narrowband PhysicalDownlink Shared CHannel NPRACH Narrowband Physical Random Access CHannelNPUSCH Narrowband Physical Uplink Shared CHannel NPSS Narrowband PrimarySynchronization Signal NSSS Narrowband Secondary Synchronization SignalNR New Radio, Neighbour Relation NRF NF Repository Function NRSNarrowband Reference Signal NS Network Service NSA Non-Standaloneoperation mode NSD Network Service Descriptor NSR Network Service RecordNSSAI ‘Network Slice Selection Assistance Information S-NNSAISingle-NSSAI NSSF Network Slice Selection Function NW Network NWUSNarrowband wake-up signal, Narrowband WUS NZP Non-Zero Power O&MOperation and Maintenance ODU2 Optical channel Data Unit-type 2 OFDMOrthogonal Frequency Division Multiplexing OFDMA Orthogonal FrequencyDivision Multiple Access OOB Out-of-band OPEX OPerating EXpense OSIOther System Information OSS Operations Support System OTA over-the-airPAPR Peak-to-Average Power Ratio PAR Peak to Average Ratio PBCH PhysicalBroadcast Channel PC Power Control, Personal Computer PCC PrimaryComponent Carrier, Primary CC PCell Primary Cell PCI Physical Cell ID,Physical Cell Identity PCEF Policy and Charging Enforcement Function PCFPolicy Control Function PCRF Policy Control and Charging Rules FunctionPDCP Packet Data Convergence Protocol, Packet Data Convergence Protocollayer PDCCH Physical Downlink Control Channel PDCP Packet DataConvergence Protocol PDN Packet Data Network, Public Data Network PDSCHPhysical Downlink Shared Channel PDU Protocol Data Unit PEI PermanentEquipment Identifiers PFD Packet Flow Description P-GW PDN Gateway PHICHPhysical hybrid-ARQ indicator channel PHY Physical layer PLMN PublicLand Mobile Network PIN Personal Identification Number PM PerformanceMeasurement PMI Precoding Matrix Indicator PNF Physical Network FunctionPNFD Physical Network Function Descriptor PNFR Physical Network FunctionRecord POC PTT over Cellular PP, PTP Point-to-Point PPP Point-to-PointProtocol PRACH Physical RACH PRB Physical resource block PRG Physicalresource block group ProSe Proximity Services, Proximity-Based ServicePRS Positioning Reference Signal PS Packet Services PSBCH PhysicalSidelink Broadcast Channel PSDCH Physical Sidelink Downlink ChannelPSCCH Physical Sidelink Control Channel PSSCH Physical Sidelink SharedChannel PSCell Primary SCell PSS Primary Synchronization Signal PSTNPublic Switched Telephone Network PT-RS Phase-tracking reference signalPTT Push-to-Talk PUCCH Physical Uplink Control Channel PUSCH PhysicalUplink Shared Channel QAM Quadmture Amplitude Modulation QCI QoS classof identifier QCL Quasi co-location QFI QoS Flow ID, QoS Flow IdentifierQoS Quality of Service QPSK Quadrature (Quaternary) Phase Shift KeyingQZSS Quasi-Zenith Satellite System RA-RNTI Random Access RNTI RAB RadioAccess Bearer, Random Access Burst RACH Random Access Channel RADIUSRemote Authentication Dial In User Service RAN Radio Access Network RANDRANDom number (used for authentication) RAR Random Access Response RATRadio Access Technology RAU Routing Area Update RB Resource block, RadioBearer RBG Resource block group REG Resource Element Group Rel ReleaseREQ REQuest RF Radio Frequency RI Rank Indicator RIV Resource indicatorvalue RL Radio Link RLC Radio Link Control, Radio Link Control layer RLFRadio Link Failure RLM Radio Link Monitoring RLM-RS Reference Signal forRLM RM Registration Management RMC Reference Measurement Channel RMSIRemaining MSI, Remaining Minimum System Information RN Relay Node RNCRadio Network Controller RNL Radio Network Layer RNTI Radio NetworkTemporary Identifier ROHC RObust Header Compression RRC Radio ResourceControl, Radio Resource Control layer RRM Radio Resource Management RSReference Signal RSRP Reference Signal Received Power RSRQ ReferenceSignal Received Quality RSSI Received Signal Strength Indicator RSU RoadSide Unit RSTD Reference Signal Time difference RTP Real Time ProtocolRTS Ready-To-Send RTT Round Trip Time Rx Reception, Receiving, ReceiverS1AP S1 Application Protocol S1-MME S1 for the control plane S1-U S1 forthe user plane S-GW Serving Gateway S-RNTI SRNC Radio Network TemporaryIdentity S-TMSI SAE Temporary Mobile Station Identifier SA Standaloneoperation mode SAE System Architecture Evolution SAP Service AccessPoint SAPD Service Access Point Descriptor SAPI Service Access PointIdentifier SCC Secondary Component Carrier, Secondary CC SCell SecondaryCell SC-FDMA Single Carrier Frequency Division Multiple Access SCGSecondary Cell Group SCM Security Context Management SCS SubcarrierSpacing SCTP Stream Control Transmission Protocol SDAP Service DataAdaptation Protocol, Service Data Adaptation Protocol layer SDLSupplementary Downlink SDNF Structured Data Storage Network Function SDPService Discovery Protocol (Bluetooth related) SDSF Structured DataStorage Function SDU Service Data Unit SEAF Security Anchor FunctionSeNB secondary eNB SEPP Security Edge Protection Proxy SFI Slot formatindication SFTD Space-Frequency Time Diversity, SFN and frame timingdifference SFN System Frame Number SgNB Secondary gNB SGSN Serving GPRSSupport Node S-GW Serving Gateway SI System Information SI-RNTI SystemInformation RNTI SIB System Information Block SIM Subscriber IdentityModule SIP Session Initiated Protocol SiP System in Package SL SidelinkSLA Service Level Agreement SM Session Management SMF Session ManagementFunction SMS Short Message Service SMSF SMS Function SMTC SSB-basedMeasurement Timing Configuration SN Secondary Node, Sequence Number SoCSystem on Chip SON Self-Organizing Network SpCell Special CellSP-CSI-RNTI Semi-Persistent CSI RNTI SPS Semi-Persistent Scheduling SQNSequence number SR Scheduling Request SRB Signalling Radio Bearer SRSSounding Reference Signal SS Synchronization Signal SSB SynchronizationSignal Block, SS/PBCH Block SSBRI SS/PBCH Block Resource Indicator,Synchronization Signal Block Resource Indicator SSC Session and ServiceContinuity SS-RSRP Synchronization Signal based Reference SignalReceived Power SS-RSRQ Synchronization Signal based Reference SignalReceived Quality SS-SINR Synchronization Signal based Signal to Noiseand Interference Ratio SSS Secondary Synchronization Signal SSTSlice/Service Types SU-MIMO Single User MIMO SUL Supplementary Uplink TATiming Advance, Tracking Area TAC Tracking Area Code TAG Timing AdvanceGroup TAU Tracking Area Update TB Transport Block TBS Transport BlockSize TBD To Be Defined TCI Transmission Configuration Indicator TCPTransmission Communication Protocol TDD Time Division Duplex TDM TimeDivision Multiplexing TDMA Time Division Multiple Access TE TerminalEquipment TEID Tunnel End Point Identifier TFT Traffic Flow TemplateTMSI Temporary Mobile Subscriber Identity TNL Transport Network LayerTPC Transmit Power Control TPMI Transmitted Precoding Matrix IndicatorTR Technical Report TRP, TRxP Transmission Reception Point TRS TrackingReference Signal TRx Transceiver TS Technical Specifications, TechnicalStandard TTI Transmission Time Interval Tx Transmission, Transmitting,Transmitter U-RNTI UTRAN Radio Network Temporary Identity UART UniversalAsynchronous Receiver and Transmitter UCI Uplink Control Information UEUser Equipment UDM Unified Data Management UDP User Datagram ProtocolUDSF Unstructured Data Storage Network Function UICC UniversalIntegrated Circuit Card UL Uplink UM Unacknowledged Mode UML UnifiedModelling Language UMTS Universal Mobile Telecommunications System UPUser Plane UPF User Plane Function URI Uniform Resource Identifier URLUniform Resource Locator URLLC Ultra-Reliable and Low Latency USBUniversal Serial Bus USIM Universal Subscriber Identity Module USSUE-specific search space UTRA UMTS Terrestrial Radio Access UTRANUniversal Terrestrial Radio Access Network UwPTS Uplink Pilot Time SlotV2I Vehicle-to-Infrastruction V2P Vehicle-to-Pedestrian V2VVehicle-to-Vehicle V2X Vehicle-to-everything VIM VirtualizedInfrastructure Manager VL Virtual Link, VLAN Virtual LAN, Virtual LocalArea Network VM Virtual Machine VNF Virtualized Network Function VNFFGVNF Forwarding Graph VNFFGD VNF Forwarding Graph Descriptor VNFM VNFManager VoIP Voice-over-IP, Voice-over-Internet Protocol VPLMN VisitedPublic Land Mobile Network VPN Virtual Private Network VRB VirtualResource Block WiMAX Worldwide Interoperability for Microwave AccessWLAN Wireless Local Area Network WMAN Wireless Metropolitan Area NetworkWPAN Wireless Personal Area Network X2-C X2-Control plane X2-U X2-Userplane XML eXtensible Markup Language XRES EXpected user RESponse XOReXclusive OR ZC Zadoff-Chu ZP Zero Power

The corresponding structures, material, acts, and equivalents of allmeans or steps plus function elements in the claims below are intendedto include any structure, material or act for performing the function incombination with other claimed elements are specifically claimed. Thedescription of the present disclosure has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the disclosure in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill without departingfrom the scope and spirit of the disclosure. The embodiments were chosenand described in order to best explain the principles of the disclosureand the practical application, and to enable others of ordinary skill inthe art to understand the disclosure for embodiments with variousmodifications as are suited to the particular use contemplated.

The foregoing description provides illustration and description ofvarious example embodiments, but is not intended to be exhaustive or tolimit the scope of embodiments to the precise forms disclosed.Modifications and variations are possible in light of the aboveteachings or may be acquired from practice of various embodiments. Wherespecific details are set forth in order to describe example embodimentsof the disclosure, it should be apparent to one skilled in the art thatthe disclosure can be practiced without, or with variation of, thesespecific details. It should be understood, however, that there is nointent to limit the concepts of the present disclosure to the particularforms disclosed, but on the contrary, the intention is to cover allmodifications, equivalents, and alternatives consistent with the presentdisclosure and the appended claims.

What is claimed is:
 1. A base station (BS), comprising: processorcircuitry configured to generate a radio resource control (RRC) messageto configure a user equipment (UE), the RRC message including a non-zeropower channel state information reference signal resource set(NZP-CSI-RS-ResourceSet) that indicates one or more non-zero powerchannel state information reference signal (NZP-CSI-RS) resources; andcommunication circuitry communicatively coupled with the processorcircuitry, the communication circuitry being configured to transmit theRRC message to the UE, wherein the communication circuitry is furtherconfigured to use same antenna ports for the NZP-CSI-RS resources in theNZP-CSI-RS-ResourceSet having a same port index based on theNZP-CSI-RS-ResourceSet including a TRS-Info parameter set to ‘on’, andwherein the communication circuitry is further configured to transmitthe NZP-CSI-RS resources in the NZP-CSI-RS-ResourceSet with a samedownlink spatial domain transmission filter based on theNZP-CSI-RS-ResourceSet including a repetition parameter set to ‘on’. 2.The BS of claim 1, wherein the RRC message comprises a soundingreference signal (SRS) configuration (SRS-Config), wherein theSRS-Config comprises one or more SRS resource sets (SRS-ResourceSets),and wherein at least one SRS-ResourceSet of the one or moreSRS-ResourceSets comprises one or more SRS resources.
 3. The BS of claim2, wherein the communication circuitry is further configured to generatethe RRC message to configure the UE with at least one SRS resource for aconfigured transmission scheme via a higher layer parameter and the atleast one SRS resource is indicated by a received downlink controlinformation (DCI) or the RRC message.
 4. The BS of claim 2, wherein theone or more SRS resources are configured to be used for one of periodicSRS transmissions, semi-persistent SRS transmissions, or aperiodic SRStransmissions.
 5. The BS of claim 2, wherein the at least oneSRS-ResourceSet includes at least one SRS resource to be used foraperiodic SRS transmissions, and wherein the communication circuitry isfurther configured to transmit downlink control information (DCI)including an SRS request field indicating the at least one SRS resourceto trigger transmission of aperiodic SRS transmissions.
 6. The BS ofclaim 1, wherein the NZP-CSI-RS-ResourceSet includes aQCL-Info-PeriodicCSl-RS parameter to indicate a transmission beam forindividual ones of the one or more NZP-CSI-RS resources.
 7. A userequipment (UE), comprising: interface circuitry configured to receive aradio resource control (RRC) message, the RRC message including anon-zero power channel state information reference signal resource set(NZP-CSI-RS-ResourceSet) that indicates one or more non-zero powerchannel state information reference signal (NZP-CSI-RS) resources; andbaseband circuitry, coupled to the interface circuitry, configured to:assume the NZP-CSI-RS resources in the NZP-CSI-RS-ResourceSet having asame port index are to be transmitted with same antenna ports based onthe NZP-CSI-RS-ResourceSet including a TRS-Info parameter set to ‘on’,and assume the NZP-CSI-RS resources in the NZP-CSI-RS-ResourceSet are tobe transmitted with a same downlink spatial domain transmission filterbased on the NZP-CSI-RS-ResourceSet including a repetition parameter setto ‘on’.
 8. The UE of claim 7, wherein only one of the TRS-Infoparameter or the repetition parameter is configured by the NZP-CSI-RSResourceSet.
 9. The UE of claim 7, wherein the RRC message comprises asounding reference signal (SRS) configuration (SRS-Config), wherein theSRS-Config comprises one or more SRS resource sets (SRS-ResourceSets),and wherein at least one SRS-ResourceSet of the one or moreSRS-ResourceSets comprises one or more SRS resources.
 10. The UE ofclaim 9, wherein the baseband circuitry is further configured to:control transmission of an SRS in the at least one SRS resource based onthe UE being configured with at least one SRS resource for a configuredtransmission scheme via a higher layer parameter and the at least oneSRS resource is indicated by a received downlink control information(DCI) or the RRC message; and control transmission of a physical uplinkshared channel (PUSCH) scheduled by DCI in a corresponding physicaluplink control channel (PUCCH) resource with a lowest resourceidentifier (ID) within an active uplink (UL) bandwidth part (BWP) basedon the UE not being configured with at least one SRS resource.
 11. TheUE of claim 9, wherein the one or more SRS resources are configured tobe used for one of periodic SRS transmissions, semi-persistent SRStransmissions, or aperiodic SRS transmissions.
 12. The UE of claim 9,wherein the at least one SRS-ResourceSet includes at least one SRSresource to be used for aperiodic SRS transmissions, and wherein thebaseband circuitry is further configured to: receive downlink controlinformation (DCI) including an SRS request field indicating the at leastone SRS resource to trigger transmission of aperiodic SRS transmissions.13. The UE of claim 7, wherein the NZP-CSI-RS-ResourceSet includes aQCL-Info-PeriodicCSI-RS parameter to indicate a transmission beam forindividual ones of the one or more NZP-CSI-RS resources.
 14. A method tobe performed by a user equipment (UE), the method comprising: receivinga radio resource control (RRC) message, the RRC message including anon-zero power channel state information reference signal resource set(NZP-CSI-RS-ResourceSet) that indicates one or more non-zero powerchannel state information reference signal (NZP-CSI-RS) resources;assuming the NZP-CSI-RS resources in the NZP-CSI-RS-ResourceSet having asame port index are to be transmitted with same antenna ports based onthe NZP-CSI-RS-ResourceSet including a TRS-Info parameter set to ‘on’;and assuming the NZP-CSI-RS resources in the NZP-CSI-RS-ResourceSet areto be transmitted with a same downlink spatial domain transmissionfilter based on the NZP-CSI-RS-ResourceSet including a repetitionparameter set to ‘on’.
 15. The method of claim 14, wherein only one ofthe TRS-Info parameter or the repetition parameter is configured by theNZP-CSI-RS ResourceSet.
 16. The method of claim 14, wherein the RRCmessage comprises a sounding reference signal (SRS) configuration(SRS-Config), wherein the SRS-Config comprises one or more SRS resourcesets (SRS-ResourceSets), and wherein at least one SRS-ResourceSet of theone or more SRS-ResourceSets comprises one or more SRS resources. 17.The method of claim 16, further comprising: controlling transmission ofan SRS in the at least one SRS resource based on the UE being configuredwith at least one SRS resource for a configured transmission scheme viaa higher layer parameter and the at least one SRS resource is indicatedby a received downlink control information (DCI) or the RRC message; andcontrolling transmission of a physical uplink shared channel (PUSCH)scheduled by DCI in a corresponding physical uplink control channel(PUCCH) resource with a lowest resource identifier (ID) within an activeuplink (UL) bandwidth part (BWP) based on the UE not being configuredwith at least one SRS resource.
 18. The method of claim 16, wherein theone or more SRS resources are configured to be used for one of periodicSRS transmissions, semi-persistent SRS transmissions, or aperiodic SRStransmissions.
 19. The method of claim 16, wherein the at least oneSRS-ResourceSet includes at least one SRS resource to be used foraperiodic SRS transmissions, and wherein the method further comprises:receiving downlink control information (DCI) including an SRS requestfield indicating the at least one SRS resource to trigger transmissionof aperiodic SRS transmissions.
 20. The method of claim 14, wherein theNZP-CSI-RS-ResourceSet includes a QCL-Info-PeriodicCSl-RS parameter toindicate a transmission beam for individual ones of the one or moreNZP-CSI-RS resources.